summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEric Anholt <eric@anholt.net>2023-10-19 10:12:16 +0200
committerMarge Bot <emma+marge@anholt.net>2023-10-23 17:59:55 +0000
commit553070f993f576b8dd0688c4548bca9035679a5b (patch)
tree9bdc6809c829bc8471400e5f77baab3fa5d94a7c
parent2ef0e6be17200487e9a2797917454a85761249eb (diff)
downloadmesa-553070f993f576b8dd0688c4548bca9035679a5b.tar.gz
mesa-553070f993f576b8dd0688c4548bca9035679a5b.tar.bz2
mesa-553070f993f576b8dd0688c4548bca9035679a5b.zip
docs/ci: Drop old instructions for farm disabling
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25806>
-rw-r--r--docs/ci/index.rst8
1 files changed, 2 insertions, 6 deletions
diff --git a/docs/ci/index.rst b/docs/ci/index.rst
index dcc2e4d9db2..2b8797200f7 100644
--- a/docs/ci/index.rst
+++ b/docs/ci/index.rst
@@ -182,12 +182,8 @@ to just run 1/10th of the test list.
If a HW CI farm goes offline (network dies and all CI pipelines end up
stalled) or its runners are consistently spuriously failing (disk
full?), and the maintainer is not immediately available to fix the
-issue, please push through an MR disabling that farm's jobs by adding
-'.' to the front of the jobs names until the maintainer can bring
-things back up. If this happens, the farm maintainer should provide a
-report to mesa-dev@lists.freedesktop.org after the fact explaining
-what happened and what the mitigation plan is for that failure next
-time.
+issue, please push through an MR disabling that farm's jobs according
+to the `Farm Management <#farm-management>`__ instructions.
Personal runners
----------------