-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Inconsistent tst-unwind-main/ctor (check-glibc) results depending on build order #1379
Comments
Two different test suites are not expected to influence each other. I just had a quick look at the disassembly of your attached files (specifically into Further analysis with Also local symbols like I believe that we have a missing dependency for the
If it works, then please file a PR. |
Some glibc tests like tst-unwind-{main,ctor} depends on stage2 artifacts (in particular, GCC runtime libs) to be properly installed. Add stage2 dependencies to avoid these tests from spuriously failing. The test suite also uses the simulator and Deja GNU, both of which were not declared as dependencies, so add them as well. Closes: riscv-collab#1379
Thanks, that works. I filed #1380. |
Some glibc tests like tst-unwind-{main,ctor} depends on stage2 artifacts (in particular, GCC runtime libs) to be properly installed. Add stage2 dependencies to avoid these tests from spuriously failing. The test suite also uses the simulator and Deja GNU, both of which were not declared as dependencies, so add them as well. Closes: riscv-collab#1379
Some glibc tests like tst-unwind-{main,ctor} depends on stage2 artifacts (in particular, GCC runtime libs) to be properly installed. Add stage2 dependencies to avoid these tests from spuriously failing. The test suite also uses the simulator and Deja GNU, both of which were not declared as dependencies, so add them as well. Closes: #1379
riscv-gnu-toolchain version: 8e9fb09
The tst-unwind-main and tst-unwind-ctor tests in glibc seems to exhibit inconsistent results depending on how the build is done.
If I run
check-glibc-linux
directly: The two tests fails.broken.zip
If I run
check-linux
first and then runcheck-glibc-linux
: The two tests passes.pass.zip
The attached files are the compiled binaries for the two tests respectively.
It's puzzling why this can happen; maybe the build order is not as expected and there's some stage1/stage2 mixup?
The text was updated successfully, but these errors were encountered: