freedreno: Introduce gitlab-based CI.
authorEric Anholt <eric@anholt.net>
Fri, 28 Jun 2019 23:35:32 +0000 (16:35 -0700)
committerEric Anholt <eric@anholt.net>
Thu, 12 Sep 2019 17:55:42 +0000 (10:55 -0700)
commit6f0dc087b7a57fb8e0cdb4b2a884086953429afd
treee1a56a7595d749f79b20fbcd13c30d0ccfd17f25
parent0b6b0c09f438c18b18a5f9e444d178767fb0bafb
freedreno: Introduce gitlab-based CI.

Since freedreno's kernel and GPU reset seem to be totally solid, we
don't need to have the complexity of the LAVA setup that panfrost has.
Instead, we can register some boards as shared gitlab runners and have
the jobs run out of a docker container just like we do for llvmpipe.
Just make sure that the DRI device node is passed through to the
containers in the gitlab config ('devices = ["/dev/dri"]' under
runners.docker).

If a runner fails (networking dies, kernel panic, etc.) it'll take out
one build but the rest can keep going since gitlab-runner is what
pulls jobs.  Since the runner pulls jobs, it also means that they can
live behind firewalls instead of needing some public address to be
accessed by gitlab.fd.o.

For now, enable it just on db410c (A307) and cheza (A630) as those are
the hardware that I have plenty of.  A307 is only testing GLES2 since
running all of GLES3 takes too long for the number of boards I've
brought up.

Acked-by: Rob Clark <robdclark@chromium.org>
Acked-by: Kenneth Graunke <kenneth@whitecape.org>
.gitlab-ci.yml
.gitlab-ci/README.md [new file with mode: 0644]
.gitlab-ci/debian-test-install.sh [new file with mode: 0644]
.gitlab-ci/deqp-freedreno-a307-fails.txt [new file with mode: 0644]
.gitlab-ci/deqp-freedreno-a630-fails.txt [new file with mode: 0644]
.gitlab-ci/deqp-freedreno-a630-skips.txt [new file with mode: 0644]