-
Notifications
You must be signed in to change notification settings - Fork 13.4k
tests/run-make/repr128-dwarf panics when LLVM assertions are enabled #138254
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
The difference is LLVM debug assertions. If you toggle I would be fine with reverting the test change (to unblock cargo subtree sync, then reland accounting for LLVM assertion differences). |
A more "minimal" profile to repro is profile = 'compiler'
[llvm]
download-ci-llvm = true
assertions = true # <- matters
[rust]
download-rustc = true # not relevant, for faster test failure only
debug-assertions = false # not relevant, for faster test failure only |
I'm not sure why this passes in CI though. |
That doesn't sound right. LLVM assertions are supposed to be enabled for all test jobs, except those marked NO_LLVM_ASSERTIONS, which is only the apple ones. |
I'll have to double check later. |
For reference, this issue is being caused by debuginfo for |
Rollup merge of rust-lang#138263 - beetrees:fix-repr128-dwarf, r=jieyouxu Fix `repr128-dwarf` test The test now correctly ignores enums from `std`. Fixes rust-lang#138254 Unblocks rust-lang#138200
The following steps illustrate the
tests/run-make/repr128-dwarf
test failing (running on x86_64-unknown-linux-gnu):This fails with the following:
This was discovered while trying to merge #138200. However, I don't think that PR is directly related given the above reproduces on latest master (currently dea1661).
I can't explain why current CI is passing, given that the above reproduces the issue (for me).
This seems to be caused by #137643
cc @beetrees @jieyouxu @weihanglo
The text was updated successfully, but these errors were encountered: