Ian Campbell f6ba03584b [clang-tidy] ensure run-clang-tidy reports children killed by signals ... If a clang-tidy child process exits with a signal then run-clang-tidy will exit with an error but there is no hint why in the output, since the clang-tidy doesn't log anything and may not even have had the opportunity to do so depending on the signal used. `subprocess.CompletedProcess.returncode` is the negative signal number in this case. I hit this in a CI system where the parallelism used exceeded the RAM assigned to the container causing the OOM killer to SIGKILL clang-tidy processes. Reviewed By: sylvestre.ledru Differential Revision: https://reviews.llvm.org/D99081		2021-07-19 14:18:26 +02:00
..
CMakeLists.txt	[clang-tidy] Install run-clang-tidy.py in bin/ as run-clang-tidy	2021-02-23 12:38:27 +00:00
ClangTidyMain.cpp	[clang-tidy] Added command line option `fix-notes`	2021-03-01 22:07:11 +00:00
ClangTidyMain.h	[clang-tidy] Add library for clang-tidy main function	2020-01-24 13:00:45 -08:00
ClangTidyToolMain.cpp	[clang-tidy] Add library for clang-tidy main function	2020-01-24 13:00:45 -08:00
clang-tidy-diff.py	add -use-color option to clang-tidy-diff.py	2021-02-18 09:12:48 -05:00
run-clang-tidy.py	[clang-tidy] ensure run-clang-tidy reports children killed by signals	2021-07-19 14:18:26 +02:00