mirrors
/
mesa
mirror of https://gitlab.freedesktop.org/mesa/mesa
1
0
Fork 0
Code Issues 9 Packages Projects Releases Wiki Activity
mesa/.gitlab-ci/deqp-freedreno-a630-skips.txt

64 lines
2.8 KiB
Plaintext
Raw Normal View History

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>
2019-06-29 00:35:32 +01:00
# Note: skips lists for CI are just a list of lines that, when
# non-zero-length and not starting with '#', will regex match to
# delete lines from the test list. Be careful.
# Skip the perf/stress tests to keep runtime manageable
ci: Make the skip list regexes match the full test name. The bash scripts were using grep in the manner that matches any subset of the line, but the new CTS runner matches the whole line and I think that's a pretty good behavior. Given that some of the skip lists already were written to match the full test name, just make them consistently do so. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Acked-by: Daniel Stone <daniels@collabora.com> Acked-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-05 17:50:40 +00:00
dEQP-GLES[0-9]*.performance.*
dEQP-GLES[0-9]*.stress.*
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>
2019-06-29 00:35:32 +01:00
# These are really slow on tiling architectures (including llvmpipe).
ci: Make the skip list regexes match the full test name. The bash scripts were using grep in the manner that matches any subset of the line, but the new CTS runner matches the whole line and I think that's a pretty good behavior. Given that some of the skip lists already were written to match the full test name, just make them consistently do so. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Acked-by: Daniel Stone <daniels@collabora.com> Acked-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-05 17:50:40 +00:00
dEQP-GLES[0-9]*.functional.flush_finish.*
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>
2019-06-29 00:35:32 +01:00
# Unstable test results
gitlab-ci/freedreno/a6xx: remove most of the flakes xfb + lines/points still flakes too frequently (and the problem isn't even related to xfb), but we can add the rest back into this mix now. Signed-off-by: Rob Clark <robdclark@chromium.org>
2019-11-21 18:54:13 +00:00
#dEQP-GLES3.functional.fragment_out.random.*
dEQP-GLES3.functional.transform_feedback.*points.*
dEQP-GLES3.functional.transform_feedback.*lines.*
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>
2019-06-29 00:35:32 +01:00
dEQP-GLES31.functional.primitive_bounding_box.*
gitlab-ci/freedreno/a6xx: remove most of the flakes xfb + lines/points still flakes too frequently (and the problem isn't even related to xfb), but we can add the rest back into this mix now. Signed-off-by: Rob Clark <robdclark@chromium.org>
2019-11-21 18:54:13 +00:00
#dEQP-GLES31.functional.layout_binding.ssbo.fragment_binding_array.*
ci: Use cts_runner for our dEQP runs. This runner is a little project by Bas, written in C++, that spawns threads that then loop grabbing chunks of the (randomly shuffled but consistently so) test list and hand it to a dEQP instance. As the remaining list gets shorter, so do the chunks, so hopefully the threads all complete effectively at once. It also handles restarting after crashes automatically. I've extended the runner a bit to do what I was doing in the bash scripts before, like the skip list and expected failures handling. This project should also be a good baseline for extending to handle retesting of intermittent failures. By switching to it, we can have the swrast tests just take up one job slot on the shared runners and keep their allotment of CPUs busy, instead of taking up job slots with single-threaded dEQP jobs. It will also let us (eventually, once I reprovision) switch the freedreno runners over to threading within the job instead of running concurrent jobs, so that memory scribbles in one pipeline don't affect unrelated pipelines, and I can experiment with their parallelism (particularly on a306 where we are frequently backed up) without trashing other people's jobs. What we lose in this process is per-test output in the log (not a big loss, I think, since we summarize fails at the end and reducing log length keeps chrome from choking on our logs so badly). We also drop the renderer sanity checking, since it's not saving qpa files for us to go poke through. Given that all the drivers involved have fail lists, if we got the wrong renderer somehow, we'd get a job failure anyway. v2: Rebase on droppong of the autoscale cluster and the arm64 build/test split. Use a script to deduplicate the cts-runner build. v3: Rebase on the amd64 build/test container split. Acked-by: Daniel Stone <daniels@collabora.com> (v1) Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> (v2)
2019-11-04 18:54:41 +00:00
# Intermittent timeout
dEQP-GLES31.functional.ssbo.layout.random.all_shared_buffer.23
ci: Bump the GLES CTS version to 3.2.6.1. This brings in the surfaceless fixes so we don't need to check out the whole repo to cherry pick any more (which was bothering me as I debugged things late in the painfully slow ARM container build process). Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3662> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3662>
2020-01-30 23:53:39 +00:00
dEQP-GLES31.functional.ssbo.layout.random.all_shared_buffer.48
ci: Disable flappy blit tests on a630. These have shown up with the new CTS runner, which has changed test ordering. Reviewed-by: Daniel Stone <daniels@collabora.com>
2019-11-12 22:01:58 +00:00
ci: Extend the a630 flake list to reduce spurious failures. These are the tests I've seen flake twice while logged in to the IRC channel this year. Also include fragment_out.random.5 which fully spuriously failed recently. Closes: #2516 Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3862> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3862>
2020-02-18 20:44:57 +00:00
# Flakes reported more than once during Jan-Feb 2020
ci: Disable a bunch of tests on freedreno a630. On a daily basis I've been having to restart people's a630 jobs in the front couple of pages of /merge_requests due to spurious failures from our flaky tests, and fielding reports of spurious fails from other developers, and babysitting my own marge merges that are failing due to our flakes. Nobody should have to deal with that, especially not non-freedreno developers, so just scrape the list of flakes reported to #freedreno-ci for the last month and ban those tests that have failed more than once until we have a credible fix. Acked-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3662>
2020-02-06 19:00:12 +00:00
dEQP-GLES31.functional.layout_binding.ssbo.fragment_binding_array
dEQP-GLES3.functional.fragment_out.random.0
dEQP-GLES3.functional.fragment_out.random.1
ci: Extend the a630 flake list to reduce spurious failures. These are the tests I've seen flake twice while logged in to the IRC channel this year. Also include fragment_out.random.5 which fully spuriously failed recently. Closes: #2516 Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3862> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3862>
2020-02-18 20:44:57 +00:00
dEQP-GLES3.functional.fragment_out.random.12
ci: Disable a bunch of tests on freedreno a630. On a daily basis I've been having to restart people's a630 jobs in the front couple of pages of /merge_requests due to spurious failures from our flaky tests, and fielding reports of spurious fails from other developers, and babysitting my own marge merges that are failing due to our flakes. Nobody should have to deal with that, especially not non-freedreno developers, so just scrape the list of flakes reported to #freedreno-ci for the last month and ban those tests that have failed more than once until we have a credible fix. Acked-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3662>
2020-02-06 19:00:12 +00:00
dEQP-GLES3.functional.fragment_out.random.13
dEQP-GLES3.functional.fragment_out.random.17
dEQP-GLES3.functional.fragment_out.random.24
dEQP-GLES3.functional.fragment_out.random.27
dEQP-GLES3.functional.fragment_out.random.28
dEQP-GLES3.functional.fragment_out.random.32
dEQP-GLES3.functional.fragment_out.random.34
dEQP-GLES3.functional.fragment_out.random.35
ci: Extend the a630 flake list to reduce spurious failures. These are the tests I've seen flake twice while logged in to the IRC channel this year. Also include fragment_out.random.5 which fully spuriously failed recently. Closes: #2516 Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3862> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3862>
2020-02-18 20:44:57 +00:00
dEQP-GLES3.functional.fragment_out.random.36
dEQP-GLES3.functional.fragment_out.random.40
ci: Disable a bunch of tests on freedreno a630. On a daily basis I've been having to restart people's a630 jobs in the front couple of pages of /merge_requests due to spurious failures from our flaky tests, and fielding reports of spurious fails from other developers, and babysitting my own marge merges that are failing due to our flakes. Nobody should have to deal with that, especially not non-freedreno developers, so just scrape the list of flakes reported to #freedreno-ci for the last month and ban those tests that have failed more than once until we have a credible fix. Acked-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3662>
2020-02-06 19:00:12 +00:00
dEQP-GLES3.functional.fragment_out.random.44
dEQP-GLES3.functional.fragment_out.random.47
ci: Extend the a630 flake list to reduce spurious failures. These are the tests I've seen flake twice while logged in to the IRC channel this year. Also include fragment_out.random.5 which fully spuriously failed recently. Closes: #2516 Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3862> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3862>
2020-02-18 20:44:57 +00:00
dEQP-GLES3.functional.fragment_out.random.5
ci: Disable a bunch of tests on freedreno a630. On a daily basis I've been having to restart people's a630 jobs in the front couple of pages of /merge_requests due to spurious failures from our flaky tests, and fielding reports of spurious fails from other developers, and babysitting my own marge merges that are failing due to our flakes. Nobody should have to deal with that, especially not non-freedreno developers, so just scrape the list of flakes reported to #freedreno-ci for the last month and ban those tests that have failed more than once until we have a credible fix. Acked-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3662>
2020-02-06 19:00:12 +00:00
dEQP-GLES3.functional.fragment_out.random.50
dEQP-GLES3.functional.fragment_out.random.51
dEQP-GLES3.functional.fragment_out.random.55
dEQP-GLES3.functional.fragment_out.random.58
dEQP-GLES3.functional.fragment_out.random.59
ci: Extend the a630 flake list to reduce spurious failures. These are the tests I've seen flake twice while logged in to the IRC channel this year. Also include fragment_out.random.5 which fully spuriously failed recently. Closes: #2516 Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3862> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3862>
2020-02-18 20:44:57 +00:00
dEQP-GLES3.functional.fragment_out.random.61
ci: Disable a bunch of tests on freedreno a630. On a daily basis I've been having to restart people's a630 jobs in the front couple of pages of /merge_requests due to spurious failures from our flaky tests, and fielding reports of spurious fails from other developers, and babysitting my own marge merges that are failing due to our flakes. Nobody should have to deal with that, especially not non-freedreno developers, so just scrape the list of flakes reported to #freedreno-ci for the last month and ban those tests that have failed more than once until we have a credible fix. Acked-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3662>
2020-02-06 19:00:12 +00:00
dEQP-GLES3.functional.fragment_out.random.63
dEQP-GLES3.functional.fragment_out.random.66
dEQP-GLES3.functional.fragment_out.random.67
dEQP-GLES3.functional.fragment_out.random.69
ci: Extend the a630 flake list to reduce spurious failures. These are the tests I've seen flake twice while logged in to the IRC channel this year. Also include fragment_out.random.5 which fully spuriously failed recently. Closes: #2516 Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3862> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3862>
2020-02-18 20:44:57 +00:00
dEQP-GLES3.functional.fragment_out.random.70
ci: Disable a bunch of tests on freedreno a630. On a daily basis I've been having to restart people's a630 jobs in the front couple of pages of /merge_requests due to spurious failures from our flaky tests, and fielding reports of spurious fails from other developers, and babysitting my own marge merges that are failing due to our flakes. Nobody should have to deal with that, especially not non-freedreno developers, so just scrape the list of flakes reported to #freedreno-ci for the last month and ban those tests that have failed more than once until we have a credible fix. Acked-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3662>
2020-02-06 19:00:12 +00:00
dEQP-GLES3.functional.fragment_out.random.71
dEQP-GLES3.functional.fragment_out.random.80
dEQP-GLES3.functional.fragment_out.random.82
dEQP-GLES3.functional.fragment_out.random.86
dEQP-GLES3.functional.fragment_out.random.88
dEQP-GLES3.functional.fragment_out.random.91
ci: Extend the a630 flake list to reduce spurious failures. These are the tests I've seen flake twice while logged in to the IRC channel this year. Also include fragment_out.random.5 which fully spuriously failed recently. Closes: #2516 Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3862> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3862>
2020-02-18 20:44:57 +00:00
dEQP-GLES3.functional.fragment_out.random.93
ci: Disable a bunch of tests on freedreno a630. On a daily basis I've been having to restart people's a630 jobs in the front couple of pages of /merge_requests due to spurious failures from our flaky tests, and fielding reports of spurious fails from other developers, and babysitting my own marge merges that are failing due to our flakes. Nobody should have to deal with that, especially not non-freedreno developers, so just scrape the list of flakes reported to #freedreno-ci for the last month and ban those tests that have failed more than once until we have a credible fix. Acked-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3662>
2020-02-06 19:00:12 +00:00
dEQP-GLES3.functional.fragment_out.random.95
dEQP-GLES3.functional.fragment_out.random.96
dEQP-GLES3.functional.transform_feedback.array_element.interleaved.triangles.highp_mat2x3
dEQP-GLES3.functional.transform_feedback.array_element.interleaved.triangles.lowp_mat2x4
dEQP-GLES3.functional.transform_feedback.array_element.separate.triangles.lowp_mat2x4