Following https://reviews.llvm.org/D155272, restrict to FAIL to ubsan-tsan tests so non-ubsan-tsan tests may still pass, shown by https://lab.llvm.org/buildbot/#/builders/179/builds/6669.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
compiler-rt/test/ubsan/TestCases/Misc/Linux/sigaction.cpp | ||
---|---|---|
8 | Build failure examples here:
clang-linux-arm64 (Not sure why these are continuing to fail after D155272):
|
compiler-rt/test/ubsan/TestCases/Misc/Linux/sigaction.cpp | ||
---|---|---|
8 | do you intend to only disable for aarch64 w/ ubsan + tsan? |
compiler-rt/test/ubsan/TestCases/Misc/Linux/sigaction.cpp | ||
---|---|---|
8 | Added ubsan-tsan to disqualifier condition to permit passing cases in https://lab.llvm.org/buildbot/#/builders/179/builds/6669:
| |
8 | Yes, so that aarch64 buliders may at least pass. It remains unclear how to handle the Linux-64 case for now, since it's not fully apparent that it impacts upstream builders. |
https://llvm.org/docs/TestingGuide.html#constraining-test-execution is helpful for figuring out the constraints, as I think the above change enables the test on more targets, instead of on all aarch64 or ubsan-tsan.
you probably want XFAIL: aarch64{{.*}, ubsan-tsan
Hey @Caslyn, looks like this unfortunately didn't fix the buildbot breakage caused by https://reviews.llvm.org/D155272, I still see UBSan-ThreadSanitizer-aarch64 :: TestCases/Misc/Linux/sigaction.cpp broken at head (https://lab.llvm.org/buildbot/#/builders/238/builds/4398).
Unexpectedly Passed Tests (1):
UBSan-ThreadSanitizer-aarch64 :: TestCases/Misc/Linux/sigaction.cpp
Do we just disable it instead of XFAIL?
I think so. We can look into reincorporating this test into that configuration once it's been determined why it fails on some builders and passes on others.
Build failure examples here:
clang-linux-x64:
clang-linux-arm64 (Not sure why these are continuing to fail after D155272):