-
Notifications
You must be signed in to change notification settings - Fork 13.3k
1.55.0 new test debuginfo/function-names.rs fails on all architectures in Debian #89750
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
Comments
IIRC we found recently this test is just not being run in our CI, so it's probably just broken. |
I'm looking into it. |
I opened #89772 to fix this. But we'll need a better long-term solution for dealing with debuginfo tests. |
…-test-gdb, r=Mark-Simulacrum Fix function-names test for GDB 10.1 This PR updates the test output in `src/test/debuginfo/function-names.rs` for GDB 10.1. This should fix issue rust-lang#89750 -- but not the underlying problem of CI ignoring tests if not viable debugger happens to be present.
…-test-gdb, r=Mark-Simulacrum Fix function-names test for GDB 10.1 This PR updates the test output in `src/test/debuginfo/function-names.rs` for GDB 10.1. This should fix issue rust-lang#89750 -- but not the underlying problem of CI ignoring tests if not viable debugger happens to be present.
Is fe3cfa0214ac55c7 endian-independent? Guess we'll see in a few days when I run this on s390x. |
The patch works on big-endian too, test passed on s390x. |
Triage: My understanding is that the failing test was fixed eventually. Let's close this issue as fixed. |
Full log, warning very large file: https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=amd64&ver=1.55.0%2Bdfsg1-1%7Eexp1&stamp=1633891056&raw=0
Note the difference:
generic_func(i32) -> i32
expected vsgeneric_func<i32>(i32) -> i32
actual output.All the other debuginfo tests are fine so I guess it's not as simple as "Debian is using the wrong GDB version"; CC @dpaoliello and @michaelwoerister who worked on the test.
The text was updated successfully, but these errors were encountered: