From 04a2f1462eed47b52afcd9be6a87d1e5c1cb5c47 Mon Sep 17 00:00:00 2001 From: Eric Anholt Date: Thu, 21 Jan 2021 13:40:47 -0800 Subject: ci/docs: Update CI farm requirements suggestions. We have a handy printout for slow tests now, and DEQP_FRACTION is now compatible with parallel. Reviewed-by: Daniel Stone Part-of: --- docs/ci/index.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'docs/ci') diff --git a/docs/ci/index.rst b/docs/ci/index.rst index 33ed30dceda..e7dea7121ea 100644 --- a/docs/ci/index.rst +++ b/docs/ci/index.rst @@ -102,11 +102,11 @@ pipeline backing up. As a result, we require that the test farm be able to handle a whole pipeline's worth of jobs in less than 15 minutes (to compare, the build stage is about 10 minutes). -If a test farm is short the HW to provide these guarantees, consider -dropping tests to reduce runtime. -``VK-GL-CTS/scripts/log/bottleneck_report.py`` can help you find what -tests were slow in a ``results.qpa`` file. Or, you can have a job with -no ``parallel`` field set and: +If a test farm is short the HW to provide these guarantees, consider dropping +tests to reduce runtime. dEQP job logs print the slowest tests at the end of +the run, and piglit logs the runtime of tests in the results.json.bz2 in the +artifacts. Or, you can add the following to your job to only run some fraction +(in this case, 1/10th) of the deqp tests. .. code-block:: yaml -- cgit v1.2.3