And XFAIL debuginfo-tests/llgdb-tests/asan-deque.cpp on !system-darwin.
On non-darwin systems these tests use gdb and this one fails because gdb
doesn't pretty-print std::deque (the elements of the deque are not printed so
the CHECK lines fail).
Details
Diff Detail
Event Timeline
We've now got a native Linux builder in staging where you can see these tests failing: https://lab.llvm.org/staging/#/builders/205/builds/91
LGTM apart from the comment below.
cross-project-tests/debuginfo-tests/llgdb-tests/asan-deque.cpp | ||
---|---|---|
8–9 | The second expression seems redundant, if !system-darwin && gdb-clang-incompatibility is true then !system-darwin is necessarily also true. Is this meant to be !system-darwin, gdb-clang-incompatibility? |
cross-project-tests/debuginfo-tests/llgdb-tests/asan-deque.cpp | ||
---|---|---|
8–9 | It is redundant yes. I figured it would be more obvious to anyone adjusting the test in the future that the second part is still necessary when the tests start passing on !system-darwin. wdyt? |
cross-project-tests/debuginfo-tests/llgdb-tests/asan-deque.cpp | ||
---|---|---|
8–9 | Seems reasonable, but might be worth expanding the below comment to specify that it applies to the !system-darwin clause, since system-darwin being essentially a proxy for "run with LLDB instead of GDB" here might not be obvious to someone unfamiliar with these tests. Something like "failing on non-darwin (gdb) builds because gdb doesn't pretty-print std::deque" or something along those lines. |
The second expression seems redundant, if !system-darwin && gdb-clang-incompatibility is true then !system-darwin is necessarily also true. Is this meant to be !system-darwin, gdb-clang-incompatibility?