We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Not sure yet why but ninja libc_setjmp_unittests fails consistently for me in fullbuild mode.
ninja libc_setjmp_unittests
$ ninja libc_setjmp_unittests [1/1] Running unit test libc.test.src.setjmp.setjmp_test FAILED: projects/libc/test/src/setjmp/CMakeFiles/libc.test.src.setjmp.setjmp_test /android0/llvm-project/build/projects/libc/test/src/setjmp/CMakeFiles/libc.test.src.setjmp.setjmp_test cd /android0/llvm-project/build/projects/libc/test/src/setjmp && /android0/llvm-project/build/projects/libc/test/src/setjmp/libc.test.src.setjmp.setjmp_test.__build__ [ RUN ] LlvmLibcSetJmpTest.SetAndJumpBack ninja: build stopped: subcommand failed.
@frobtech mentioned that there were issues in our implementation; guessing that's related.
The text was updated successfully, but these errors were encountered:
@llvm/issue-subscribers-libc
Author: Nick Desaulniers (nickdesaulniers)
$ ninja libc_setjmp_unittests [1/1] Running unit test libc.test.src.setjmp.setjmp_test FAILED: projects/libc/test/src/setjmp/CMakeFiles/libc.test.src.setjmp.setjmp_test /android0/llvm-project/build/projects/libc/test/src/setjmp/CMakeFiles/libc.test.src.setjmp.setjmp_test cd /android0/llvm-project/build/projects/libc/test/src/setjmp && /android0/llvm-project/build/projects/libc/test/src/setjmp/libc.test.src.setjmp.setjmp_test.__build__ [ RUN ] LlvmLibcSetJmpTest.SetAndJumpBack ninja: build stopped: subcommand failed.
Sorry, something went wrong.
nickdesaulniers
No branches or pull requests
Not sure yet why but
ninja libc_setjmp_unittests
fails consistently for me in fullbuild mode.@frobtech mentioned that there were issues in our implementation; guessing that's related.
The text was updated successfully, but these errors were encountered: