[all-commits] [llvm/llvm-project] f6ba03: [clang-tidy] ensure run-clang-tidy reports childre...

[Ian Campbell via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: f6ba03584b3ce5dab45d8c1fe84e89d4d668574d
      https://github.com/llvm/llvm-project/commit/f6ba03584b3ce5dab45d8c1fe84e89d4d668574d
  Author: Ian Campbell <ijc at hellion.org.uk>
  Date:   2021-07-19 (Mon, 19 Jul 2021)

  Changed paths:
    M clang-tools-extra/clang-tidy/tool/run-clang-tidy.py

  Log Message:
  -----------
  [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