-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
#116787 broke ui-fulldeps on stage1 #116867
Comments
#116009 was supposed to prevent this :( |
Oh no, anything I can do to help fix this? Whether or not it's directly related to my changes, I'm happy to help with a fix. |
At a glance, it looks like the test for this is only run in PR CI? If that's true, then running the test there doesn't prevent this situation. If it's wrong, a good step would be bisecting or just going through all the commits in that rollup to see if anything jumps out when you run |
My understanding is that that's caused by stage1 I'm not sure how to proceed given that, though. If running stage0 instead of stage1 is a workaround to avoid some underlying issue, maybe it's worth trying to fix that, but other than that I'm not sure if there's a way to fix this other than waiting for stage0 to be updated for that PR. Not to say there isn't a way, I'm just not experienced enough to know it. If there's something that can be done, I can take care of it with a push in the right direction. Thoughts? |
I believe it's the opposite, it's supposed to only run on merges not on PRs. The fun fact is that this test indeed failed during the merge IIUC https://github.com/rust-lang-ci/rust/actions/runs/6551562742/job/17793020957#step:24:18909 |
Fix x86_64-gnu-llvm-15 CI tests The CI script was broken - if there was a test failure in the first command chain (inside the `if`), CI would not report the failure. It happened because there were two command chains separated by `&&` in the script, and since `set -e` doesn't exit for chained commands, if the first chain has failed, the script would happily continue forward, ignoring any test failures. This could be fixed e.g. by adding some `|| exit 1` to the first chain, but I suppose that the `&&` chaining is unnecessary here anyway. Reported [on Zulip](https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/test.20failure.20didn't.20stop.20CI). Fixes: rust-lang/rust#116867
Since #116787
I ran
x test
withThe text was updated successfully, but these errors were encountered: