-
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
windows: x.py test failure from codegen test suite #96464
Comments
Also reproduces on Linux too so not Windows specific. As for why it didn't fail in CI but does locally: the test is marked with:
and far as I can tell most targets are built with debug assertions in CI and hence will ignore the test altogether. e.g. here:
Looks like both the "compiler" and "codegen" config.toml profiles by default don't enable debug-assertions which may be why you ran into it. @rustbot label: -O-windows -O-windows-msvc |
Those changes were deliberate, since reverting #92419 introduced additional panics which made the test fail locally. Before #92419, I believe the test passed by accident--the string It looks like the test has now returned to that original state. Less inlining is occuring, and again |
Ah ok, thanks for clarifying! |
The test is known to fail on Windows: rust-lang/rust#96464 R=collinbaker@chromium.org Bug: 1271215 Change-Id: Ic7fda651e5a8ae5e9ebcd565415716d9d9e5c8b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4226612 Reviewed-by: Collin Baker <collinbaker@google.com> Commit-Queue: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/main@{#1101810}
This test has started failing on Linux and Mac with TOT LLVM (again?) Linux
Mac
|
rust-lang/rust#96464 The test used to fail on Windows only but now fails everywhere. The Rust CI skips this test as they run in debug mode and the test does not run in Debug mode, so we will hit failures before upstream does here. This failure is likely being hit due to TOT LLVM though, which upstream does not use. R=hans@chromium.org Bug: 1401042 Change-Id: Ie379559f318f3b7bd57c5db4cd21806218bcb373 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4517966 Commit-Queue: danakj <danakj@chromium.org> Reviewed-by: Hans Wennborg <hans@chromium.org> Cr-Commit-Position: refs/heads/main@{#1141656}
I tried this code (on Windows, in powershell)
I got this output:
Here's a gist with more complete output: https://gist.github.com/pnkfelix/343528a3da2000880b370a22b6010b99
This all might be an artifact of weirdnesses in how I work, like putting the build products into their own subdirectory,
objdir
, of the rust.git source repo. Not sure yet.The text was updated successfully, but these errors were encountered: