DavidSpickett wrote: > especially given we run ninja with -k 0.
To explain to future readers / current reviewers, add: "-k 0 builds as much as possible until everything has completed or failed, rather than stopping after 1 command fails". At least that's my understanding of it. This gets me in llvm-test-suite logs too. Clang will crash and print a bit of the error report, then in the long time it takes to generate the backtrace, other logs get printed. Then again, it's nice for the build to go as far as possible so you can fix multiple things each time. https://github.com/llvm/llvm-project/pull/152621 _______________________________________________ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
