GitLab

Erico Nunes authored Mar 27, 2022 and Marge Bot committed May 23, 2022

Fix the syntax to show the files in the generated sphinx, otherwise
they just don't show at all.
Signed-off-by: Erico Nunes <nunes.erico@gmail.com>
Reviewed-by: Emma Anholt <emma@anholt.net>
Part-of: <!15599>

Emma Anholt authored Jan 23, 2022 and Marge Bot committed Mar 09, 2022

Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
Part-of: <!15201>

Emma Anholt authored Jan 23, 2022 and Marge Bot committed Mar 09, 2022

We haven't been using initramfs in a long time, don't point people that
direction.  Do point people at existing instances of these CI variants,
though.
Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
Part-of: <!15201>

The NFS method is much faster.
Signed-off-by: Christian Gmeiner <christian.gmeiner@gmail.com>
Reviewed-by: Emma Anholt <emma@anholt.net>
Part-of: <!11611>

Reviewed-by: Eric Anholt <eric@anholt.net>
Part-of: <!9947>

We need a newline here to avoid syntax errors while builind the
sphinx-documentation.

The errors don't lead the build fail, so we didn't notice this on CI.
Which is a shame IMO. Instead, the blocks simply fail to render.

Fixes: 2e2edaa8

 ("docs/ci: Document setting up the http cache for traces.")
Reviewed-by: Eric Anholt <eric@anholt.net>
Part-of: <mesa/mesa!8839>

Reviewed-by: Daniel Stone <daniel@fooishbar.org>
Part-of: <!8727>

I've set it up in the gitlab-runer config on all the freedreno boards.
This means that for piglit, where the run.sh always choose either this
variable or 4 threads otherwise, we'll have the right number of parallel
tasks.
Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
Part-of: <!7370>

Signed-off-by: Andres Gomez <agomez@igalia.com>
Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Part-of: <!6388>

Reviewed-by: Eric Engestrom <eric@engestrom.ch>
Part-of: <!6915>

Reviewed-by: Eric Engestrom <eric@engestrom.ch>
Part-of: <!6915>

Reviewed-by: Eric Anholt <eric@anholt.net>
Part-of: <!6894>

Reviewed-by: Eric Engestrom <eric@engestrom.ch>
Part-of: <mesa/mesa!6864>

Closes: mesa/mesa#2655

Signed-off-by: Christian Gmeiner <christian.gmeiner@gmail.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
Part-of: <mesa/mesa!5661>

Saw a couple myself, and a quick round of vimspell showed a bunch more.
Signed-off-by: Eric Engestrom <eric@engestrom.ch>
Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com>
Part-of: <mesa/mesa!5814>

I tried not to edit too much meaning in the process, but I did shuffle
some stuff around to work as structured documentation.
Reviewed-by: Eric Engestrom <eric@engestrom.ch>
Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com>
Part-of: <!5510>

This will let us:

- deploy kernels for testing code depending on new kernel featuers
- Ensure a pristine state in the HW before starting our tests
- Avoid disk rot on the chezas taking them out (we'd lost 3/9 in a few
  months).
Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com>
Part-of: <!5247>

This supports powering up the device (using an external tool you
provide based on your particular lab), talking over serial to wait for
the fastboot prompt, and then booting a fastboot image on a target
device.

I was previously relying on LAVA for this, but that ran afoul of
corporate policies related to the AGPL.  However, LAVA wasn't doing
too much for us, given that gitlab already has a job scheduler and
tagging and runners.  We were spending a lot of engineering on making
the two systems match up, when we can just have gitlab do it directly.
Lightly-reviewed-by: Kristian H. Kristensen <hoegsberg@google.com>
Tested-by: Marge Bot <!4076>
Part-of: <!4076>