Clemens Backes 26b0eb6746 [inspector][test] Fail on non-zero return code ... While writing a new test I realized that the test did not fail if running into a CHECK or UNREACHABLE *after* printing the last expected line. That is because both stderr and the exit status are ignored. This CL fixes that. This will uncover a lot of memory leaks, which I plan to address in follow-up CLs. R=machenbach@chromium.org CC=​szuend@chromium.org Bug: chromium:1142437, v8:11107 Cq-Include-Trybots: luci.v8.try:v8_linux64_asan_rel_ng Cq-Include-Trybots: luci.v8.try:v8_mac64_asan_rel_ng Cq-Include-Trybots: luci.v8.try:v8_win64_asan_rel_ng Change-Id: I65f325abf102e063bb4f449353c47e94d84de652 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2519567 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#71006}		2020-11-06 11:35:44 +00:00
..
__init__.py	[test] Check output on the worker process.	2018-01-04 14:12:31 +00:00
base.py	[inspector][test] Fail on non-zero return code	2020-11-06 11:35:44 +00:00
message.py	[test] Work around Android linker warning in message tests	2020-06-26 15:05:32 +00:00
mkgrokdump.py	Python2 compatibility: fix flake8 report F632 F821	2019-04-05 16:24:19 +00:00
mozilla.py	[test] Check output on the worker process.	2018-01-04 14:12:31 +00:00
test262.py	[tools] Generate additional variant for FAIL_PHASE_ONLY tests	2018-12-13 11:28:57 +00:00
webkit.py	[test] Check output on the worker process.	2018-01-04 14:12:31 +00:00