-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
fix rustc build with llvm head #96362
Comments
There's a patch for this at #96215. |
It builds now, but at least on our bots, src/test/ui/numeric/numeric-cast.rs fails with trunk LLVM: https://ci.chromium.org/ui/p/chromium/builders/try/linux_upload_clang/2200/overview => https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket/8815915618951615473/+/u/package_rust/stdout?format=raw
(And many more lines of output before that.) |
#96229 is specifically about the interaction with JSON parsing that makes the failure extra non-obvious. |
Hm, someone on #94322 says "#94327 should help with this specific instance", but that's been merged a while ago. So I guess #94322 covers something more general than the specific instance fixed by that change. If the test doesn't consistently pass, the failure is understood, and a fix won't happen soon, maybe that test should be disabled for now? |
@chbaker0 too :) |
Opened #96551 to try and remove the nondeterminism based on the path length, which should alleviate the problem (it fixed the |
…mulacrum Add compiletest and bootstrap "--skip" option forwarded to libtest With this PR, "x.py test --skip SKIP ..." will run the specified test suite, but forward "--skip SKIP" to the test tool. libtest already supports this option. The PR also adds it to compiletest which itself just forwards it to libtest. Adds the functionality requested in rust-lang#96342. This is useful to work around tests broken upstream. rust-lang#96362 (comment) is the specific test issue my project is trying to work around.
…lacrum Add compiletest and bootstrap "--skip" option forwarded to libtest With this PR, "x.py test --skip SKIP ..." will run the specified test suite, but forward "--skip SKIP" to the test tool. libtest already supports this option. The PR also adds it to compiletest which itself just forwards it to libtest. Adds the functionality requested in rust-lang#96342. This is useful to work around tests broken upstream. rust-lang#96362 (comment) is the specific test issue my project is trying to work around.
…iating, r=Mark-Simulacrum [compiletest] Ignore known paths when abbreviating output To prevent out of memory conditions, compiletest limits the amount of output a test can generate, abbreviating it if the test emits more than a threshold. While the behavior is desirable, it also causes some issues (like rust-lang#96229, rust-lang#94322 and rust-lang#92211). The latest one happened recently, when the `src/test/ui/numeric/numeric-cast.rs` test started to fail on systems where the path of the rust-lang/rust checkout is too long. This includes my own development machine and [LLVM's CI](rust-lang#96362 (comment)). Rust's CI uses a pretty short directory name for the checkout, which hides these sort of problems until someone runs the test suite on their own computer. When developing the fix I tried to find the most targeted fix that would prevent this class of failures from happening in the future, deferring the decision on if/how to redesign abbreviation to a later date. The solution I came up with was to ignore known base paths when calculating whether the output exceeds the abbreviation threshold, which removes this kind of nondeterminism. This PR is best reviewed commit-by-commit.
building rust started failing like so:
Need to update rust code to work after https://reviews.llvm.org/D124216 (createAddressSanitizerFunctionPass, createModuleAddressSanitizerLegacyPassPass removal, https://reviews.llvm.org/D123882 populateThinLTOPassManager removal).
6234a56 has a related example.
@nikic Do you know if Augie (or anyone else) has a patch for this already?
@adetaylor
The text was updated successfully, but these errors were encountered: