-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Pretend in bootstrap snapshot tests that we always build in-tree LLVM #143474
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
I'm not 100%, would like to double-check this change in #143126. |
IIUC, this is because the CI configuration is changing the test input? |
We will need to normalize more things in the bootstrap test config, yeah. I don't understand why the LLVM build step disappeared though, when LLVM was modified, it should be built, not downloaded, so if anything the step should appear (but really it should be called in both cases). |
Yeah, it should be unconditionally called (a no-op step is fine), but it should still appear... |
@bors r+ p=1 (bootstrap fix blocking other PRs) |
Pretend in bootstrap snapshot tests that we always build in-tree LLVM Otherwise, depending on whether CI LLVM is inhibited or if an externally-provided LLVM is used, bootstrap host LLVM build step could be missing in step snapshots. Note that I'm not sure if this is the *right* solution (this might be *a* solution). I imagine we do want to control for the set of configuration that these snapshot tests are run, as much as possible. r? `@Kobzol`
Otherwise, depending on whether CI LLVM is inhibited or if an externally-provided LLVM is used, bootstrap host LLVM build step could be missing in step snapshots.
Note that I'm not sure if this is the right solution (this might be a solution). I imagine we do want to control for the set of configuration that these snapshot tests are run, as much as possible.
r? @Kobzol