Michael Achenbach ee56a9863e [test] Run heavy tests sequentially ... This adds a new status file indicator "HEAVY" to mark tests with high resource demands. There will be other tests running in parallel, but only a limited number of other heavy tests. The limit is controlled with a new parameter --max-heavy-tests and defaults to 1. The change also marks a variety of tests as heavy that recently had flaky timeouts. Heavy also implies slow, hence heavy tests are executed at the beginning with a higher timeout like other slow tests. The implementation is encapsulated in the test-processor chain. A new processor buffers heavy tests in a queue and adds buffered tests only if other heavy tests have ended their computation. Bug: v8:5861 Change-Id: I89648ad0030271a3a5af588ecc9c43285b728d6d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2905767 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Liviu Rau <liviurau@chromium.org> Cr-Commit-Position: refs/heads/master@{#74712}		2021-05-21 12:59:49 +00:00
..
testdata	[test] Run heavy tests sequentially	2021-05-21 12:59:49 +00:00
__init__.py	[test] make python recognize tools and tools/unittests as packages	2018-12-17 12:12:43 +00:00
compare_torque_output_test.py	[torque] Add support for torque output comparison	2020-01-21 14:39:04 +00:00
predictable_wrapper_test.py	[test] Move predictable testing into a python wrapper	2017-12-08 14:46:10 +00:00
run_perf_test.py	[test] Make finding build directory more flexible	2020-09-28 12:38:16 +00:00
run_tests_test.py	[test] Run heavy tests sequentially	2021-05-21 12:59:49 +00:00
v8_presubmit_test.py	[test] add an option for disabling linter cache in the pre_submit check	2018-12-18 15:37:09 +00:00