aboutsummaryrefslogtreecommitdiffstats
path: root/.gitlab-ci
Commit message (Collapse)AuthorAgeFilesLines
* gitlab-ci: configure the Vulkan ICD export with VK_DRIVERSamuel Pitoiset2019-12-061-0/+8
| | | | | Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* gitlab-ci: allow to run dEQP Vulkan with DEQP_VERSamuel Pitoiset2019-12-061-7/+14
| | | | | Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Michel Dänzer <[email protected]>
* gitlab-ci: build dEQP VK 1.1.6 in the x86 test image for VKSamuel Pitoiset2019-12-062-1/+39
| | | | | Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Michel Dänzer <[email protected]>
* gitlab-ci: build cts_runner in the x86 test image for VKSamuel Pitoiset2019-12-061-1/+5
| | | | | Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Michel Dänzer <[email protected]>
* gitlab-ci: add a new job that builds a base test image for VKSamuel Pitoiset2019-12-061-0/+70
| | | | | Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Michel Dänzer <[email protected]>
* gitlab-ci: add a gl suffix to the x86 test image and all test jobsSamuel Pitoiset2019-12-061-0/+0
| | | | | Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Michel Dänzer <[email protected]>
* gitlab-ci: rename build-deqp.sh to build-deqp-gl.shSamuel Pitoiset2019-12-063-4/+4
| | | | | Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Michel Dänzer <[email protected]>
* gitlab-ci: Use the common run policy for LAVA jobs as well againMichel Dänzer2019-12-061-16/+2
| | | | | | | | | | | | Having different policies could have some weird results, e.g. changes only touching documentation (where the intention is not to run the pipeline by default) would still create a pipeline with the LAVA jobs running by default. Reviewed-by: Samuel Pitoiset <[email protected]> Reviewed-by: Pierre-Eric Pelloux-Prayer <[email protected]> Reviewed-by: Tomeu Vizoso <[email protected]> Acked-by: Eric Engestrom <[email protected]>
* llvmpipe: enable support for primitives generated outside streamoutDave Airlie2019-12-061-17/+2
| | | | | | This enables the draw support when the queries are enabled. Reviewed-by: Roland Scheidegger <[email protected]>
* llvmpipe: disable occlusion queries when requested by state trackerDave Airlie2019-12-061-4/+2
| | | | Reviewed-by: Roland Scheidegger <[email protected]>
* ci: Disable egl_ext_device_drm tests in piglit.Eric Anholt2019-12-051-8/+3
| | | | | | | | | | | | | | | If the runner has a HW device that would be supported, even without /dev/dri forwarded into the container, it will be enumerated and the tests on llvmpipe fail with (for example): libEGL warning: Not allowed to force software rendering when API explicitly selects a hardware device. libEGL warning: MESA-LOADER: failed to open i965 (search paths /builds/anholt/mesa/install/lib/dri) Given that we can't necessarily control the DRI devices present on the runners (particularly for developers bringing their own runners to reduce the demands on fd.o's shared resources), just skip these tests in CI. Reviewed-by: Michel Dänzer <[email protected]>
* gitlab-ci: bump piglit checkout commitTapani Pälli2019-12-043-7/+24
| | | | | | | | Commit also updates the Piglit quick_gl.txt, list modifications happened due to following Piglit commits: c248bf201,c acff58ca, 5603e2e60. Signed-off-by: Tapani Pälli <[email protected]> Reviewed-by: Timothy Arceri <[email protected]>
* gitlab-ci: Run piglit glslparser & quick_shader tests separatelyMichel Dänzer2019-12-043-6509/+5319
| | | | | | | | | | | And only use --process-isolation false for the quick_gl tests. This will hopefully avoid variance in the test results that we've been seeing lately. But even if it doesn't, it should at least help narrow down the cause of the variance. Tested-by: Vasily Khoruzhick <[email protected]> Acked-by: Pierre-Eric Pelloux-Prayer <[email protected]>
* gitlab-ci: Update to current ci-templates masterMichel Dänzer2019-12-031-1/+1
| | | | | | Fixes skopeo copy failures. Reviewed-by: Pierre-Eric Pelloux-Prayer <[email protected]>
* Add support for T820 CI JobsNeil Armstrong2019-12-035-3/+75
| | | | | | | Tomeu: - Small rebase fixups Signed-off-by: Neil Armstrong <[email protected]> Signed-off-by: Tomeu Vizoso <[email protected]>
* gitlab-ci: Test Panfrost on T720 GPUsTomeu Vizoso2019-12-035-4/+63
| | | | | | | | Now that the Mali T720 GPU is supoprted at the same level as the T760, test it on PINE64 H64 boards. Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Alyssa Rosenzweig <[email protected]>
* gitlab-ci: Remove non-default skips from PanfrostAlyssa Rosenzweig2019-12-034-103/+9
| | | | | | | | | During the past months, Panfrost has matured considerably and several tests stopped being flaky or failing at all. Signed-off-by: Alyssa Rosenzweig <[email protected]> Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Alyssa Rosenzweig <[email protected]>
* gitlab-ci: Put HTML summary in artifacts for failed piglit jobsMichel Dänzer2019-11-271-0/+2
| | | | | | | This will make it easier to look at details of failed / skipped tests. Acked-by: Daniel Stone <[email protected]> Reviewed-by: Eric Anholt <[email protected]>
* gitlab-ci: Stop storing piglit test results as JUnitMichel Dänzer2019-11-273-5522/+13614
| | | | | | | | | | Since we're not reporting test results as JUnit anymore, we can use the default JSON format. This affects how test results are summarized, update the reference files accordingly. Reviewed-by: Eric Anholt <[email protected]>
* llvmpipe: initial query buffer object support. (v2)Dave Airlie2019-11-251-5/+4
| | | | | | | This fails a couple of piglits due to other bugs in llvmpipe, but it adds support for the feature properly. v2: don't reset pipestats, just recalc, fix CI expectation
* ci: Use a tag from the parallel-deqp-runner repo.Eric Anholt2019-11-221-1/+1
| | | | | | | If the repo continues development, we don't want to accidentally pick up potentially breaking changes on our next container rebuild. Reviewed-by: Eric Engestrom <[email protected]>
* gitlab-ci/freedreno/a6xx: remove most of the flakesRob Clark2019-11-221-19/+4
| | | | | | | 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 <[email protected]>
* gitlab-ci/deqp: generate junit resultsRob Clark2019-11-221-0/+27
| | | | | Signed-off-by: Rob Clark <[email protected]> Acked-by: Eric Engestrom <[email protected]>
* gitlab-ci/deqp: generate xml results for fails/flakesRob Clark2019-11-221-0/+40
| | | | | | | | | | | | | Extract .qpa for the individual unexpected results and flakes, and translate to xml, preserved with the artifacts. This allows easy browsing of the test logs for fails/flakes, for easier debugging. The # of logs to preserve is capped at 50 to avoid saving 100s of megabytes of logs in case someone pushes a change that breaks everything. Signed-off-by: Rob Clark <[email protected]> Acked-by: Eric Engestrom <[email protected]>
* gitlab-ci: bump arm test containerRob Clark2019-11-221-0/+3
| | | | | | | To pick up updated cts_runner and netcat for the flake reporting. Signed-off-by: Rob Clark <[email protected]> Acked-by: Eric Engestrom <[email protected]>
* gitlab-ci/deqp: detect and report flakesRob Clark2019-11-222-9/+73
| | | | | | | | | | | | | If there are a small number of fails, re-run to determine if they are flakes, and optionally (if `$FLAKES_CHANNEL` configured) report the flakes. This way flakes don't interfere with developers working on other drivers, but get logged so that the developers working on the flaking driver can monitor the situation. Signed-off-by: Rob Clark <[email protected]> Acked-by: Eric Engestrom <[email protected]>
* gitlab-ci/deqp: preserve caselists for blocks with failsRob Clark2019-11-222-3/+5
| | | | | | | | | | Bump cts_runner to pick up the change to preserve .qpa and caselist .txt files for blocks of tests that contain fails, and preserve the caselist files. To reproduce fails that depend on order of running tests, these are useful. Signed-off-by: Rob Clark <[email protected]> Acked-by: Eric Engestrom <[email protected]>
* gitlab-ci/deqp: preserve full list of unexpected resultsRob Clark2019-11-221-3/+5
| | | | | | | | | | | The log only shows the first 50, but preserve the full list for easier browsing. (Also move return of exit code to end which makes later patches in the series easier) Signed-off-by: Rob Clark <[email protected]> Acked-by: Eric Engestrom <[email protected]>
* gitlab-ci: update deqp build so we can generate xmlRob Clark2019-11-221-1/+11
| | | | | | | | | | | | | | | | Update the deqp build to preserve testlog-to-xml and stylesheets, so deqp runner can extract .qpa for failed/flaked tests, and convert to xml. With this, will be able to browse output from failed tests directly from the artifacts. The main motiviation is to give better visibility into what happens with flaked tests, when it is difficult/impossible to reproduce the flake locally (ie. when it happens once out of N million tests). But this should also make it easier to debug regressions that a MR triggers, especially when it is on hw that you don't have. Signed-off-by: Rob Clark <[email protected]> Acked-by: Eric Engestrom <[email protected]>
* gitlab-ci: move building piglit into a separate scriptSamuel Pitoiset2019-11-212-10/+14
| | | | | Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Michel Dänzer <[email protected]>
* gitlab-ci: Fix dir name for VK-GL-CTS sourcesTomeu Vizoso2019-11-201-1/+1
| | | | | Signed-off-by: Tomeu Vizoso <[email protected]> Acked-by: Alyssa Rosenzweig <[email protected]>
* gitlab-ci: update for arb_shading_language_includeTimothy Arceri2019-11-202-15/+5
|
* gitlab-ci: bump piglit checkout commitTimothy Arceri2019-11-201-1/+1
|
* gitlab-ci: Remove limit on kernel loggingTomeu Vizoso2019-11-191-1/+0
| | | | | | | | | We don't seem to fault any more when running dEQP GLES2, and we don't scrape serial output any more anyway so no problems should be caused by that. Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Alyssa Rosenzweig <[email protected]>
* mesa: enable EXT_direct_state_accessPierre-Eric Pelloux-Prayer2019-11-191-17/+2
| | | | | | | | | | Always enabled; this doesn't require any driver work, it's just core mesa bits. quick_gl.txt is also updated because previously piglit ext_dsa tests were skipped. Reviewed-by: Marek Olšák <[email protected]>
* gitlab-ci: Organize images using new REPO_SUFFIX templates featureMichel Dänzer2019-11-151-10/+13
| | | | | | | | | | | | | | | Two benefits: Most docker image related environment variables can now be defined in the jobs where they're used instead of globally. The DEBIAN_TAG values are propagated to other jobs via YAML anchors. Images on https://gitlab.freedesktop.org/mesa/mesa/container_registry are now organized in separate repositories with a suffix matching the name of the job which makes sure the image is there. Acked-by: Eric Anholt <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* gitlab-ci: Rename container install scripts to match job names (better)Michel Dänzer2019-11-157-2/+1
| | | | | | | | | | | | Cleans up .gitlab-ci/ a little, and allows using a single DEBIAN_EXEC line for all container jobs. v2: * Use lava_arm.sh instead of arm_lava.sh for consistency with v2 of the previous change Reviewed-by: Eric Anholt <[email protected]> # v1 Reviewed-by: Eric Engestrom <[email protected]>
* gitlab-ci: Use functional container job namesMichel Dänzer2019-11-151-6/+6
| | | | | | | | | | | This makes it easier to tell which job is which in a pipeline. v2: * Use lava_arm{64,hf} instead of arm{64,hf}_lava to keep these jobs together in pipeline overviews Reviewed-by: Eric Anholt <[email protected]> # v1 Reviewed-by: Eric Engestrom <[email protected]>
* gitlab-ci: Document that ci-templates refs must be in syncMichel Dänzer2019-11-151-0/+1
| | | | | | | | | | | Otherwise there can be weird breakage. (Removing the include from .gitlab-ci/lava-gitlab-ci.yml doesn't seem possible unfortunately: https://gitlab.freedesktop.org/daenzer/mesa/pipelines/79458) Reviewed-by: Eric Anholt <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* panfrost: Multiply offset_units by 2Tomeu Vizoso2019-11-152-4/+0
| | | | | | | | | | Per the spec, the units passed to glPolygonOffset are to be multiplied by an implementation-defined constant. On Midgard, this constant seems to be 2. Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Alyssa Rosenzweig <[email protected]>
* gitlab-ci: update Piglit commit, update skipsTapani Pälli2019-11-153-5/+7
| | | | | Signed-off-by: Tapani Pälli <[email protected]> Reviewed-by: Michel Dänzer <[email protected]>
* gitlab-ci: auto-cancel CI runs when a newer commit is pushed to the same branchEric Engestrom2019-11-141-0/+2
| | | | | | | Signed-off-by: Eric Engestrom <[email protected]> Reviewed-by: Eric Anholt <[email protected]> Acked-by: Alyssa Rosenzweig <[email protected]> Reviewed-by: Michel Dänzer <[email protected]>
* ci: Expand the freedreno blit skip regex to cover more cases.Eric Anholt2019-11-131-1/+1
| | | | | | | | We've had flaps on at least: - r16f_to_r16f - r16i_to_rg16i Reviewed-by: Daniel Stone <[email protected]>
* pan/midgard: Add blend shader selection bits for MRTAlyssa Rosenzweig2019-11-131-6/+0
| | | | | | | | | | | | | This is less complicated than previously thought. Note we have no way of specifying the work register count for blend shaders; it must be strictly less than the work register count of the corresponding fragment shader (which is fine since we force the fragment shader to report a count of 16 with a blend shader as a major hack until we get register pressure down for blend shaders). TODO: pandecode the flags. Signed-off-by: Alyssa Rosenzweig <[email protected]>
* gitlab-ci: build a specific libdrm version for ARM64Samuel Pitoiset2019-11-131-1/+8
| | | | | | | RADV requires libdrm-2.4.100 but the distrib package is too old. Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Eric Engestrom <[email protected]>
* ci: Disable flappy blit tests on a630.Eric Anholt2019-11-121-0/+4
| | | | | | | These have shown up with the new CTS runner, which has changed test ordering. Reviewed-by: Daniel Stone <[email protected]>
* ci: Remove old commented copy of freedreno artifacts.Eric Anholt2019-11-121-1/+0
| | | | This path was from an older version of freedreno CI.
* ci: Enable all of GLES3/3.1 testing for softpipe.Eric Anholt2019-11-122-0/+415
| | | | | | | | Now that we're not using so many job slots, it's easy to get these jobs run in a reasonable amount of time (gles3 took 10 minutes for 4 cores, and gles31 was 15 minutes for 4 cores). Acked-by: Michel Dänzer <[email protected]>
* ci: Use cts_runner for our dEQP runs.Eric Anholt2019-11-125-79/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <[email protected]> (v1) Reviewed-by: Tomeu Vizoso <[email protected]> (v2)
* ci: Make the skip list regexes match the full test name.Eric Anholt2019-11-122-7/+7
| | | | | | | | | | | | 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 <[email protected]> Acked-by: Daniel Stone <[email protected]> Acked-by: Michel Dänzer <[email protected]>
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-29 23:18:22 +0000