This test fails for Clang versions < 14.0 for dsym variants.
dsymutil strips debug info for classes with only static members.
Thus move the failing assertions into the XFAIL test case.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
This might be a bit aggressive. If it's easy we could add a if clang > 14 condition before those last two tests so we don't loose coverage?
Fair point, I moved the assertions to a new XFAIL test-case which is specific to dsym Clang 14.0 variants
This test is now failing even on the "basic" Clang (i.e. tip of trunk) test matrix entry:
The log above is for the "Test DWARF4" portion of the job
That's very confusing, will have to check what the debug info looks like on the machines
Looking at the logs, the Dwarf 2 and Dwarf 4 jobs do not use ToT, but rather Clang 13. For example, for the Dwarf 2 job, we see this:
"/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/clang_1300_build/bin/clang" -std=c++11 -gdwarf-2 -isysroot
Which is weird, given how we don't build Clang 13 until much later on the pipeline.
I think the bot has a polluted environment somehow across runs. For example, build 5042:
ERROR:root:/Users/buildslave/jenkins/workspace/lldb-cmake-matrix/clang_1300_build/bin/clang is not a valid compiler executable; aborting...
Sometimes the Clang13 builds get cleaned up (see how sometimes the Clang 13 jobs take 30s to run, and sometimes 40min).
I'm guessing that this error shows up when the previous build got cleaned up.
Yup that would explain why this sometimes passes (only the times where we use top-of-tree clang). Confident now that this change will fix the Clang < 14.0 tests.
Greendragon is leaking environment configurations across runs. I'll address this in a separate PR