ldionne added a comment. Most of the libc++ CI testing happens on BuildKite, and we only trigger the libc++ buildkite pipeline if files in `libcxx/` (and a few others) have changed. This wasn't the case here. If you want to re-land without breaking libc++, you'd have to go through libc++'s `.verify.cpp` tests and change the regex that we look for.
Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D129048/new/ https://reviews.llvm.org/D129048 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
