-
Notifications
You must be signed in to change notification settings - Fork 13.8k
Re-enable assertions on macOS alt builds #146513
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
@bors try |
Re-enable assertions on macOS try-job: `*apple*`
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
💔 Test for beeae75 failed: CI. Failed jobs:
|
Reminder, once the PR becomes ready for a review, use |
This comment has been minimized.
This comment has been minimized.
Re-enable assertions on macOS try-job: `*apple*`
@bors try cancel |
Try build cancelled. Cancelled workflows: |
2bdfca2
to
b2c7b6b
Compare
@bors try |
Re-enable assertions on macOS try-job: `*apple*`
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
💔 Test for 56e5725 failed: CI. Failed jobs:
|
This wasn't caught by CI, because debug assertions aren't enabled there.
b2c7b6b
to
25bedcd
Compare
@bors try |
Re-enable assertions on macOS try-job: `*apple*`
This comment has been minimized.
This comment has been minimized.
25bedcd
to
9878be7
Compare
So, the |
Re-enable assertions on macOS try-job: `*apple*`
This comment has been minimized.
This comment has been minimized.
So, I think this works! r? @Mark-Simulacrum since you're on t-infra and were assigned to #59637 in the past. Also CC @jieyouxu, since you've tried to do this in the past. |
I'm unsure if it has a performance impact, comparing it against the
Which feels like wayy too high a variance to really be able to say anything conclusive? |
This PR changes a file inside |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit confused. This appears to enable assertions on a bunch of dist targets, but distributed toolchains are not supposed to enable assertions.
Should this change be limited to only aarch64-apple, which is a test target and as such should enable assertions?
Right, the That said, it this will allow others to enable |
@bors r+ rollup=never This seems reasonable to me. Thanks! I agree that the CI times don't seem affected (at least within noise reasonable to achieve from a single PR's measurements). |
…ulacrum Re-enable assertions on macOS alt builds These were previously disabled, in part for performance reasons, in part due to needing availability symbols `__isPlatformVersionAtLeast` and `__isOSVersionAtLeast` that `compiler-builtins` did not provide, see #62592 (comment) and #134275 (comment) for failed checks. Since #138944 though, `std` now provides these symbols, so we should be able to re-enable LLVM assertions, debug assertions and overflow checks. Fixes #59637. try-job: `*apple*`
These were previously disabled, in part for performance reasons, in part due to needing availability symbols
__isPlatformVersionAtLeast
and__isOSVersionAtLeast
thatcompiler-builtins
did not provide, see #62592 (comment) and #134275 (comment) for failed checks.Since #138944 though,
std
now provides these symbols, so we should be able to re-enable LLVM assertions, debug assertions and overflow checks.Fixes #59637.
try-job:
*apple*