Those were missed by https://llvm.org/D111477, which broke the CI.
Details
- Reviewers
dblaikie - Group Reviewers
Restricted Project - Commits
- rG9904bcf2a487: [libc++] Fix GDB pretty printer tests for older Clangs and GCC
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Event Timeline
Since we install the nightly ToT Clang (which is clang-14) on our CI machines, it turns out that this still fails for clang-14. It will fail until the Docker images pick up a ToT Clang that contains D111477, but we don't really have control over when that happens.
That's not a great story for rolling out changes to Clang and libc++ in lockstep, we need to figure out how to do that better. Ideally we'd build Clang ToT in each job before running the tests, but that is going to be prohibitively expensive.
For now, I'm going to mark the test as UNSUPPORTED on clang-14 until the builders pick up something recent enough. Not great but it should get the CI green again.
Does the matching here support regex? We could make the tests format agnostic instead? (hmm, maybe the internal stuff in lldb isn't format agnostic, though... )
"This revision was not accepted when it landed; it landed in state Needs Review."
I guess since libc++'s Phab is configured to require review from a libc++ maintainer (Since I did approve it, but that didn't take it out of the "Needs Review" state, I guess?) ? Could that be fixed in some way, since it doesn't seem to match the reality of what's expected here?