docs: Relax the expectations of HW CI farms.

We've been doing pretty well at around half an hour per pipeline, no need
to be too harsh.

Reviewed-by: Eric Engestrom <eric@engestrom.ch>
Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5510>

diff --git a/docs/ci/index.rst b/docs/ci/index.rst
index 4055f876f9135b0f9bfbf2c0bdedc9e28988438d..e191d471f0d798cec2c77de3c0a187da5c234be1 100644 (file)
--- a/docs/ci/index.rst
+++ b/docs/ci/index.rst
@@ -99,9 +99,8 @@ unacceptable cost to the project.
 Additionally, the test farm needs to be able to provide a short enough
 turnaround time that we can get our MRs through marge-bot without the
 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 5 minutes
-(to compare, the build stage is about 10 minutes, if you could get all
-your jobs scheduled on the shared runners in time.).
+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.