[Lldb-commits] [PATCH] D132004: [lldb][Tests] Skip static-only tests in TestConstStaticIntegralMember.py for dsym variant

[Michael Buch via Phabricator via lldb-commits]

Michael137 added a comment.

In D132004#3728652 <https://reviews.llvm.org/D132004#3728652>, @fdeazeve wrote:

> In D132004#3728394 <https://reviews.llvm.org/D132004#3728394>, @fdeazeve wrote:
>
>> This test is now failing even on the "basic" Clang (i.e. tip of trunk) test matrix entry:
>>
>> https://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake-matrix/5043/execution/node/62/log/?consoleFull
>>
>> The log above is for the "Test DWARF4" portion of the job
>
> 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:
>
> https://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake-matrix/5042/execution/node/52/log/?consoleFull
>
>> 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.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D132004/new/

https://reviews.llvm.org/D132004