diff options
| author | bors <bors@rust-lang.org> | 2019-05-30 19:52:11 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2019-05-30 19:52:11 +0000 |
| commit | 3ade426ede7bca4a74bc641a12f2e7fe2cc20c47 (patch) | |
| tree | e170debb73827a02d1e897c292c440e0775d4ae8 /src/test/ui/thinlto | |
| parent | 0bfbaa6e8dfb509b453020740fd37c7a22882c87 (diff) | |
| parent | ebdf42e9650a969bef553a0886d3754a670bd335 (diff) | |
| download | rust-3ade426ede7bca4a74bc641a12f2e7fe2cc20c47.tar.gz rust-3ade426ede7bca4a74bc641a12f2e7fe2cc20c47.zip | |
Auto merge of #61353 - alexcrichton:less-tools, r=pietroalbini
ci: Favor SCRIPT instead of RUST_CHECK_TARGET Since #61212 we've been timing out on OSX, and this looks to be because we're building tools like Cargo and the RLS twice instead of once. This turns out to be a slight bug in our configuration. CI builders using the `RUST_CHECK_TARGET` directive actually execute `make all` just before their acual target. In `make all` we're building a stage2 cargo, and then in `make dist` we're building a stage1 cargo. Other builders use `SCRIPT` which provides explicit control over what `x.py` script, for example, is used to execute the build. This moves almost all targets to using `SCRIPT` to ensure that we're explicitly specifying what's being built where. Additionally this updates the logic of `RUST_CHECK_TARGET` to remove the pre-flight tidy as well as the pre-flight `make all`. The system LLVM builder (run on PRs) now explicitly runs tidy first and then runs the rest of the test suite.
Diffstat (limited to 'src/test/ui/thinlto')
0 files changed, 0 insertions, 0 deletions
