about summary refs log tree commit diff
path: root/src/ci/docker/x86_64-gnu-distcheck
AgeCommit message (Collapse)AuthorLines
2020-07-03ci: move all x86_64 runners to the host-x86_64 directoryPietro Albini-30/+0
We need to add runners designed for an aarch64 host system, and it'd be nice to return an error message if someone tries to run an image designed for an host architecture in another one. To start the work on this, this commit moves all the existing builders in the host-x86_64 directory, and changes the run.sh script to look up the image in the correct directory based on the host architecture.
2020-04-10Enforce Python 3 as much as possibleGuillaume Gomez-2/+2
2019-06-06ci: Disable LLVM/debug assertions for distcheckAlex Crichton-0/+7
The purpose of distcheck is to test `./x.py test` from a tarball, not to test that all assertions pass all the time. These assertions are largely just redundant with other builders, so skip the assertions for now and save a good chunk of time on CI. cc #61185
2017-08-29fix option for RUST_CONFIGURE_ARGS to be rust.ignore-git=falseJeremy Sorensen-1/+1
2017-08-29change option for RUST_CONFIGURE_ARGS to ignore-git=falseJeremy Sorensen-1/+1
2017-08-29add ignore-git=true option to RUST_CONFIGURE_ARGSJeremy Sorensen-1/+1
2017-08-26ci: Remove the need for `dumb-init`Alex Crichton-5/+0
Newer versions of Docker have a `--init` argument which spawns an init process in the container, which we should be able to use everywhere now.
2017-07-12Updated docker images to factor out common scriptsTy Coghlan-6/+5
2017-05-12Update sccache binaries to mozilla/sccache@d3627d766Alex Crichton-1/+1
This commit updates the sccache binaries to fix a cache load failure seen on #41926, fixed by mozilla/sccache#119
2017-04-29ci: Update sccache buildAlex Crichton-1/+1
Pulls in mozilla/sccache@ef0d77543 to fix #40240 again after the builds included in #41447 forgot to include the mio fixed included in #41076. Closes #40240
2017-04-27appveyor: Use Ninja/sccache on MSVCAlex Crichton-1/+1
Now that the final bug fixes have been merged into sccache we can start leveraging sccache on the MSVC builders on AppVeyor instead of relying on the ad-hoc caching strategy of trigger files and whatnot.
2017-04-27travis: Update sccache build usedAlex Crichton-1/+1
This build is no longer a forked version with temporary bugfixes, everything should be upstreamed!
2017-04-04travis: Update sccache binariesAlex Crichton-1/+1
I've tracked down what I believe is the last spurious sccache failure on #40240 to behavior in mio (carllerche/mio#583), and this commit updates the binaries to a version which has that fix incorporated.
2017-03-24travis: Update sccache againAlex Crichton-1/+1
Looks like the last version was built with mio 0.6.5 which now has known bugs against it. This build includes mio 0.6.6
2017-03-23travis: Update sccache binaryAlex Crichton-1/+1
2017-03-16travis: Update sccache binaryAlex Crichton-1/+1
I've built a local copy with mozilla/sccache#79 and mozilla/sccache#78. Let's see if that helps #40240!
2017-02-27appveyor: Use sccache on pc-windows-gnu for cachingAlex Crichton-1/+1
Now that mozilla/sccache#43 is fixed the caching works for MinGW on Windows. We still can't use it for MSVC just yet, but I'll try to revive that branch at some point.
2017-02-24Update sccache binaries on CIAlex Crichton-3/+3
Currently CI builds can fail spuriously during the LLVM build (#39003). I believe this is due to sccache, and I believe that in turn was due to the fact that the sccache server used to just be a raw mio server. Historically raw mio servers are quite complicated to get right, but this is why we built Tokio! The sccache server has been migrated to Tokio which I suspect would fix any latent issues. I have no confirmation of this (never been able to reproduce the deadlock locally), but my hunch is that updating sccache to the master branch will fix the timeouts during the LLVM build. The binaries previously came from Gecko's infrastructure, but I've built new ones by hand for Win/Mac/Linux and uploaded them to our CI bucket.
2017-02-15travis: Disable source tarballs on most buildersAlex Crichton-0/+1
Currently we create a source tarball on almost all of the `DEPLOY=1` builders but this has the adverse side effect of all source tarballs overriding themselves in the S3 bucket. Normally this is ok but unfortunately a source tarball created on Windows is not buildable on Unix. On Windows the vendored sources contain paths with `\` characters in them which when interpreted on Unix end up in "file not found" errors. Instead of this overwriting behavior, whitelist just one linux builder for producing tarballs and avoid producing tarballs on all other hosts.
2017-02-14Automatically vendor Cargo deps when building the source tarballs.Eduard-Mihai Burtescu-1/+3
2017-01-12travis: Start uploading artifacts on commitsAlex Crichton-1/+1
This commit starts adding the infrastructure for uploading release artifacts from AppVeyor/Travis on each commit. The idea is that eventually we'll upload a full release to AppVeyor/Travis in accordance with plans [outlined earlier]. Right now this configures Travis/Appveyor to upload all tarballs in the `dist` directory, and various images are updated to actually produce tarballs in these directories. These are nowhere near ready to be actual release artifacts, but this should allow us to play around with it and test it out. Once this commit lands we should start seeing artifacts uploaded on each commit. [outlined earlier]: https://internals.rust-lang.org/t/rust-ci-release-infrastructure-changes/4489
2016-12-30travis: Add a distcheck targetAlex Crichton-0/+26
This commit adds a new entry to the Travis matrix which performs a "distcheck", which basically means that we create a tarball, extract that tarball, and then build/test inside there. This ensures that the tarballs we produce are actually able to be built/tested! Along the way this also updates the rustbuild distcheck definition to propagate the configure args from the top-level invocation. Closes #38691