about summary refs log tree commit diff
path: root/compiler/rustc_lexer/src
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2024-02-04 15:14:19 +0000
committerbors <bors@rust-lang.org>2024-02-04 15:14:19 +0000
commit671eb38a4e5fadb75548841ec7ae31224eea0593 (patch)
tree04f6fc06272e49a157d7c1f0ca0464b9c6e623d4 /compiler/rustc_lexer/src
parentb11fbfbf351b94c7eecf9e6749a4544a6d4717fa (diff)
parent2aebe6c302088dcd75ae18f40b40f6860c505450 (diff)
downloadrust-671eb38a4e5fadb75548841ec7ae31224eea0593.tar.gz
rust-671eb38a4e5fadb75548841ec7ae31224eea0593.zip
Auto merge of #120543 - ehuss:macos-ninja, r=Mark-Simulacrum
CI: Use ninja on apple builders

This switches the apple builders to use ninja when building LLVM. My hope is that this should resolve the timeouts we have been experiencing since December. My theory is that something in the image update from [Dec 20](https://github.com/actions/runner-images/commit/dec20a5272b8878f400fa2dc6588de003391d5a8) is causing an issue with our build (or, perhaps more remotely, some [update to LLVM itself](https://github.com/rust-lang/rust/commits/master/src/llvm-project)).

The symptoms are that during the LLVM build it just hangs just before the install step. The last thing it prints is `[100%] Built target llvm-reduce` and then just hangs. Normally the next part should be `Install the project...` where it starts installing LLVM. I'm able to reproduce this without too much difficulty. I've been testing ninja, and it seems to be working better (however, my test isn't quite equivalent, since I'm getting sccache misses, and I can't update the S3 bucket).

Installing ninja takes about 7 to 10 seconds, so it shouldn't impact things. I can't determine if it will affect the overall build timing due to not being able to test with a warm S3 cache.
Diffstat (limited to 'compiler/rustc_lexer/src')
0 files changed, 0 insertions, 0 deletions