aboutsummaryrefslogtreecommitdiffstats
path: root/.gitlab-ci/deqp-freedreno-a630-fails.txt
Commit message (Collapse)AuthorAgeFilesLines
* gitlab-ci/a630: Drop the MSAA expected failure.Eric Anholt2019-09-131-1/+0
| | | | | | | | | This hasn't failed for me in ~5 minutes of looping over dEQP-GLES3.functional.fbo.msaa.* Reviewed-by: Adam Jackson <[email protected]> Acked-by: Rob Clark <[email protected]> Reviewed-by: Kristian H. Kristensen <[email protected]>
* gitlab-ci/a630: Drop remaining dEQP-GLES3.functional.draw.random.* xfails.Eric Anholt2019-09-131-2/+0
| | | | | | | | | These haven't failed for me in ~10 minutes of looping over draw.random.*. Reviewed-by: Adam Jackson <[email protected]> Acked-by: Rob Clark <[email protected]> Reviewed-by: Kristian H. Kristensen <[email protected]>
* freedreno: Introduce gitlab-based CI.Eric Anholt2019-09-121-0/+6
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 <[email protected]> Acked-by: Kenneth Graunke <[email protected]>