-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Revert "Auto merge of #107224 - nikic:llvm-16, r=cuviper" #109326
Conversation
@bors r+ p=1 |
📌 Commit 253a28a26c59ed0c5fbcc6f282eecb9c0dd60a8c has been approved by It is now in the queue for this repository. |
🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened. |
@bors p=100 |
⌛ Testing commit 253a28a26c59ed0c5fbcc6f282eecb9c0dd60a8c with merge fba87d696a7fd31dcf564b235f0a890e1841289a... |
💔 Test failed - checks-actions |
Oh, looks like @bors r=the8472 |
📌 Commit b612a926d394b893505ccd8d2fe9e4ab2c989cc4 has been approved by It is now in the queue for this repository. |
⌛ Testing commit b612a926d394b893505ccd8d2fe9e4ab2c989cc4 with merge 54e311fb4fc2425e1f7e4716285390f5e7b57743... |
💔 Test failed - checks-actions |
I would guess you need to bump |
Ah, this also reverted the fix to is_ci_llvm_available(), so it wasn't detected as an LLVM update. Next try... @bors r=the8472 |
⌛ Testing commit 4192743 with merge 5f0d7702b680eba8973ebc2bb48e001296f125d4... |
FYI, I'm still getting a SIGSEGV locally with this PR. |
The LLVM PR was the last one that succeded though: https://github.com/rust-lang-ci/rust/actions |
💔 Test failed - checks-actions |
@bors retry seems like a spurious os error? |
Yeah, seems to have happened before: #107504 (comment) |
☀️ Test successful - checks-actions |
@bors treeclosed- |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (ab9bb3e): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
|
This is a revert of a recently merged PR, so the overall perf effect of the original PR and this one is nil. @rustbot label: +perf-regression-triaged |
The job Click to see the possible cause of the failure (guessed by this bot)
|
The job Click to see the possible cause of the failure (guessed by this bot)
|
This reverts commit 4a04d08, reversing changes made to 2d0a7de.
The LLVM 16 upgrade is almost certainly responsible for the CI segfaults that were observed after it landed, looking something like this:
r? @ehuss