aboutsummaryrefslogtreecommitdiffstats
path: root/.gitlab-ci/lava-gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* gitlab-ci: Re-add kernels for bare-metalTomeu Vizoso2020-07-171-2/+4
| | | | | | | | | | | I mistakenly removed what I thought were remnants of when Freedreno used LAVA for their DUTs. lava_arm.sh is used for baremetal, so re-add that code. Fixes: dcd171f5e9bd ("gitlab-ci: More stable URL for kernel and ramdisk artifacts, for LAVA") Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Eric Anholt <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5839>
* gitlab-ci: Run all of GLES3 tests for PanfrostTomeu Vizoso2020-07-161-2/+1
| | | | | | | | | | | We have enough capacity now and Panfrost should be very near to GLES3 compliance. v2: Update fails list (Alyssa) Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Alyssa Rosenzweig <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5932>
* gitlab-ci: Drop dependencies:Michel Dänzer2020-07-141-4/+0
| | | | | | | | | | | Artifacts from jobs listed in needs: are downloaded by default, so there's no need to list them in dependencies: as well (in fact, https://docs.gitlab.com/ce/ci/yaml/#artifact-downloads-with-needs says using dependencies: together with needs: is invalid, so we might have been getting lucky...). Reviewed-by: Tomeu Vizoso <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5845>
* gitlab-ci: Don't rebuild kernels and rootfs if they have been already built ↵Tomeu Vizoso2020-07-091-1/+8
| | | | | | | | | in mainline Use the ones from mainline if possible to save cycles rebuilding the same files. Signed-off-by: Tomeu Vizoso <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5822>
* gitlab-ci: Remove left-behind rules:Tomeu Vizoso2020-07-091-2/+2
| | | | | | | | | | | | | | It's something that was added to ease development, but that was supposed to be removed before merging. It also causes problems when arm-related jobs aren't enabled, as arm_build is needed by these jobs but in that case isn't there. Also extend from .ci-run-policy. Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Michel Dänzer <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5802>
* gitlab-ci: More stable URL for kernel and ramdisk artifacts, for LAVATomeu Vizoso2020-07-071-21/+33
| | | | | | | | | | | | | | | | | | | | | Place the kernel and ramdisk into a place in the file server so the URL will only change when the contents also change. Also put the Mesa build into a separate tarball so the ramdisk's contents don't change every build. With proper caching in place, all devices in the same farm need only to download the mesa tarball once, saving time. As we switch to MinIO for making kernels and rootfs available to LAVA devices, we can stop using Docker to distribute them. Instead, build when needed in separate jobs that push directly to MinIO, from where LAVA devices can download them. Signed-off-by: Tomeu Vizoso <[email protected]> Acked-by: Daniel Stone <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5515>
* CI: Re-enable Panfrost T860 jobsDaniel Stone2020-06-301-2/+2
| | | | | | | | The lab is back online. This reverts commit 34db50558d9a6dca89218f74c4418cdf0b0acbcb. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5694>
* CI: Temporarily disable Panfrost T860 jobsDaniel Stone2020-06-301-2/+2
| | | | | | | | | | | Phase two of our network reconfiguration is happening this afternoon, so we need to drop our RK3399 out for a little while. (Part of this reconfiguration is to shard our devices across networks and racks, so losing one part of our infrastructure doesn't mean losing any particular device type.) Signed-off-by: Daniel Stone <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5689>
* CI: Disable Panfrost Mali-T820, Lima Mali-400 and Lima Mali-450 jobsKenneth Graunke2020-06-231-3/+3
| | | | | | | The runners appear to be unhealthy. Disable for now so people can merge patches for other drivers in the meantime. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5619>
* Revert "CI: Disable Panfrost Mali-T820 jobs"Neil Armstrong2020-06-181-1/+1
| | | | | | | | | | | This reverts commit 46a32f0b6bf91279d001a4905babe4e50007696e. The lab has recovered health, thus re-enable T820 Panfrost jobs. Acked-by: Michel Dänzer <[email protected]> Reviewed-by: Tomeu Vizoso <[email protected]> Signed-off-by: Neil Armstrong <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4727>
* Revert "CI: Disable Lima jobs due to lab unhealthiness"Neil Armstrong2020-06-181-2/+2
| | | | | | | | | | | This reverts commit adeef43d15092a6910dceb3605f5ee3151dd2c47. The lab has recovered health, thus re-enable Lima jobs. Acked-by: Michel Dänzer <[email protected]> Reviewed-by: Tomeu Vizoso <[email protected]> Signed-off-by: Neil Armstrong <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4727>
* Revert "CI: Disable Panfrost T720/T760"Daniel Stone2020-06-021-2/+2
| | | | | | | | | | Switches have been rewired, VLANs have been reconfigured, network elements with non-functional remote management have been removed from racks and thrown on desks in anger. This reverts commit ae6e1aee7d1bd49ae494b8a25ca33d092a3a145a. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5301>
* CI: Disable Panfrost T720/T760Daniel Stone2020-06-021-2/+2
| | | | | | | | | | | | | | We're reconfiguring our Cambridge office lab networking and physical setup for more scalability amongst other things. We can still run jobs on one RK3399 at the peak outage, but we'll lose the T7x0 this morning, so disable it until it's all back. T820 is still disabled due to an unrelated BayLibre internal outage. Signed-off-by: Daniel Stone <[email protected]> Reviewed-by: Michel Dänzer <[email protected]> Reviewed-by: Eric Anholt <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
* CI: Re-enable Panfrost T7x0 jobsDaniel Stone2020-05-121-2/+2
| | | | | | | | | | The hardware issue in the lab preventing jobs from being run on those machines (and limiting T820 availability), leading to them being disabled in !4965, has been fixed. Signed-off-by: Daniel Stone <[email protected]> Fixes: 696bafac40f5 ("CI: Disable Panfrost T7x0 jobs") Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5006>
* CI: Disable Panfrost T7x0 jobsDaniel Stone2020-05-081-2/+2
| | | | | | | | | One of the dispatchers in the office (with all the T7x0 boards) has gone AWOL, and we don't have physical access to restore it. Disable it until we can get in and fix it. Signed-off-by: Daniel Stone <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4965>
* ci: Add sanity checking that dEQP gets the expected GL_RENDERER.Eric Anholt2020-04-271-7/+7
| | | | | | | | | | It's easy to get something wrong in the driver build or container or something that results in falling back to swrast, and then your only clue was runtime and how your failure cases suspiciously match a swrast driver's. Reviewed-by: Tomeu Vizoso <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4621>
* CI: Disable Lima jobs due to lab unhealthinessDaniel Stone2020-04-191-2/+2
| | | | | | | The BayLibre LAVA host appears to be down. Signed-off-by: Daniel Stone <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4631>
* gitlab-ci/lava: Add needs: for container image to test jobs (again)Michel Dänzer2020-04-071-0/+2
| | | | | | | | | | | | | Without this, the test jobs could spuriously run after the container job failed or was cancelled, even if the build job didn't run at all. (I already did this in 94cfe590703018cf3d34a0c1f8667064919bf843, but it got dropped accidentally in 22d976454f4e50142116f4544c0bbf11134ce991) Reviewed-by: Adam Jackson <[email protected]> Acked-by: Alyssa Rosenzweig <[email protected]> Reviewed-by: Pierre-Eric Pelloux-Prayer <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4432>
* Revert "gitlab-ci: Disable jobs for Collabora's LAVA lab"Tomeu Vizoso2020-03-281-4/+4
| | | | | | | | | | Lab is online again. This reverts commit 1351ee03352b12690233a73e160f92da2edecf16. Signed-off-by: Tomeu Vizoso <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4347> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4347>
* CI: Disable Panfrost Mali-T820 jobsDaniel Stone2020-03-271-1/+1
| | | | | | | | The BayLibre T820 runners appear to be unhealthy. Signed-off-by: Daniel Stone <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4359> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4359>
* gitlab-ci: Disable jobs for Collabora's LAVA labTomeu Vizoso2020-03-271-4/+4
| | | | | | | | | The lab is going down for a few hours to upgrade the LAVA installation to the latest stable release. Signed-off-by: Tomeu Vizoso <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4342> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4342>
* gitlab-ci: re-enable mali400/450 and t820 jobsNeil Armstrong2020-03-261-6/+6
| | | | | | | | | | | | | The FILES_HOST_NAME and FILES_HOST_URL are in the baylibre's runner environment to make it more flexible. Also use the new aarch64 mesa-ci-aarch64-lava-baylibre runner with embedded nginx server to serve the LAVA artifacts. Signed-off-by: Neil Armstrong <[email protected]> Reviewed-by: Tomeu Vizoso <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4295> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4295>
* gitlab-ci: add FILES_HOST_URL and move FILES_HOST_NAME into jobsNeil Armstrong2020-03-261-5/+9
| | | | | | | | | | The FILES_HOST_URL & FILES_HOST_NAME will be in the Baylibre's runner environment, move them into the t860/t720/t760 jobs using Collabora's runner. Signed-off-by: Neil Armstrong <[email protected]> Reviewed-by: Tomeu Vizoso <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4295>
* gitlab-ci: Serve files for LAVA via separate serviceTomeu Vizoso2020-03-261-9/+21
| | | | | | | | | | | | | | | | | Currently, we store the kernel and ramdisk for each LAVA job in the artifacts of the job that built them. Because artifacts are stored in GCE and LAVA labs aren't, this causes a lot of egress with is expensive. To avoid this, have runners download most of the data via the (cached) container images once, and for each job upload the kernel and ramdisk to a server outside GCE. Right now we only have Collabora's runner with a local web server, so jobs that go to Baylibre's lab have been disabled. Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Eric Anholt <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4295>
* Revert "ci: Remove T820 from CI temporarily"Neil Armstrong2020-03-161-1/+1
| | | | | | | | | | | | | This reverts commit 089c8f0b8da86a05bde8359c84085e0b795abf17. Our office changes are finished and power is now stable in our lab for T820 CI to run again. Cc: Daniel Stone <[email protected]> Cc: Tomeu Vizoso <[email protected]> Signed-off-by: Neil Armstrong <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4057> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4057>
* ci: Make a simple little bare-metal fastboot mode for db410c.Eric Anholt2020-03-111-19/+0
| | | | | | | | | | | | | | | | | 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 <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4076> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4076>
* gitlab-ci: rules:changes to test on tested drivers changesPierre-Eric Pelloux-Prayer2020-03-091-16/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For now tests only use these drivers: * llvmpipe * softpipe * freedreno * lima * etnaviv * panfrost So using rules:changes gitlab feature to run the tests when the changes made are potentially affecting these drivers. A few notes: * the following code: .piglit-test: extends: - .test-gl - .llvmpipe-rules makes gitlab replace .test-gl "rules:changes" values by the one from ".llvmpipe-rules". * rules:changes always matches for non-MR new branches so jobs will always be created (and they'll be run if their dependencies are run). For pushes to existing branches the files changed by the push are used to match the rules:changes path. * the same gitlab feature could be used for some build jobs Acked-by: Eric Engestrom <[email protected]> Reviewed-by: Michel Dänzer <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/2569> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/2569>
* gitlab-ci: Always name artifacts archive after the job producing itMichel Dänzer2020-03-071-0/+1
| | | | | | | | | | | | | This will help determine which artifacts generate how much traffic. v2: * Add "mesa_" prefix to make it obvious which project the artifacts are from. Reviewed-by: Samuel Pitoiset <[email protected]> Reviewed-by: Eric Anholt <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4085> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4085>
* gitlab-ci: Distribute jobs across more stagesMichel Dänzer2020-03-051-1/+8
| | | | | | | | | | | | | | The stages and mapping of jobs to them are somewhat arbitrary; the goal is to avoid having to scroll through large numbers of jobs. v2: (Pierre-Eric Pelloux-Prayer) * Use even more stages for test jobs * Give somewhat meaningful names to stages Reviewed-by: Pierre-Eric Pelloux-Prayer <[email protected]> Reviewed-by: Eric Engestrom <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3995> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3995>
* ci: Flip db410c back to docker mode.Eric Anholt2020-03-031-2/+2
| | | | | | | | | | Turns out there's corporate policy to not deploy AGPL software, so I have to take down the LAVA lab until we sort out how to do it without a local server. Reviewed-by: Daniel Stone <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4038> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4038>
* ci: Add a disabled-by-default job for GLES3 testing on db410c.Eric Anholt2020-03-021-0/+6
| | | | | | | | | | | | | | Now that we have 7 (soon 8) boards available, there's capacity to be testing GLES 3.0. However, due to (it looks like) buffer overflows in the driver, we end up with flaky test results: 1/60 jobs spuriously failed, and another 6/60 jobs reported flakes. At 6 jobs per pipeline, that's way too high of a failure rate to enable for non-freedreno developers. Leave the job present but disabled so that we can do manual test runs for regressions. Reviewed-by: Daniel Stone <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3661> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3661>
* ci: Switch testing on db410c over to LAVA.Eric Anholt2020-03-021-0/+11
| | | | | | | | | | | | | | | | | | | This should get us better stability of the db410c boards by having a smaller per-board software stack, with no disks involved (just initramfs). Additionally, the new cluster is 7 (soon 8) db410cs, while currently the docker cluster only has 1/4 of its db410cs still running. Unfortunately, we have to prepare the fastboot boot image during the ARM drivers build stage, because LAVA relies on publicly available URLs for the images to load into the bootloaders of the boards, and the only thing we have for that is gitlab's artifacts. Note that this testing relies on the boards being freshly flashed with the linaro v136 firmware to pick up the initramfs size fixes and to stop the boot at fastboot. Reviewed-by: Daniel Stone <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3661>
* Revert "gitlab-ci: disable panfrost runners"Daniel Stone2020-03-021-4/+4
| | | | | | | | | | | | | The infrastructure issues, caused by building electrical works gone wrong, have been fixed, and the Panfrost LAVA runners are available again. This reverts commit a86662c44d7cb2541c3f613805533064219ad11f. Signed-off-by: Daniel Stone <[email protected]> Reviewed-by: Tomeu Vizoso <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4019> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4019>
* gitlab-ci: disable panfrost runnersIlia Mirkin2020-03-011-4/+4
| | | | | | | | | They seem to be timing out. Signed-off-by: Ilia Mirkin <[email protected]> Reviewed-by: Daniel Stone <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4011> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4011>
* gitlab-ci: Use PAN_MESA_DEBUG=gles3 for PanfrostTomeu Vizoso2020-02-271-5/+5
| | | | | | | | | We can drop now the GLES version overrides now that we have a DEBUG flag that enables all what is expected from a GLES 3.0 implementation. Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Alyssa Rosenzweig <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3950>
* gitlab-ci: Run GLES3 tests in dEQP on PanfrostTomeu Vizoso2020-02-261-6/+25
| | | | | | | | | | We are able to run only 1/5th of the tests in around the same time that dEQP-GLES2 takes, so do that for now while more DUTs are installed. Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Eric Anholt <[email protected]> Reviewed-by: Alyssa Rosenzweig <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3876>
* gitlab-ci: Enable the lima job againAndreas Baierl2020-02-251-1/+1
| | | | | | | | | | | Flaky tests should be fixed to the best of our knowledge. Fails and skips lists should be up-to-date again. Reviewed-by: Vasily Khoruzhick <[email protected]> Reviewed-by: Tomeu Vizoso <[email protected]> Signed-off-by: Andreas Baierl <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3884> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3884>
* ci: Remove a useless filtering of the lava logs.Eric Anholt2020-02-211-1/+1
| | | | | | | | | | | We don't print every case any more, so no need to filter them out. This makes it so the output form "lavacli jobs logs" gets line-buffered into "tee" and you can actually see what happened when the job is stuck but before it times out. Reviewed-by: Tomeu Vizoso <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3883> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3883>
* gitlab-ci: Disable the lima job for nowTomeu Vizoso2020-02-201-1/+1
| | | | | | | | | | | Some dEQP tests have started passing and it's taking a while to update the expectations and skips list. Disable for now so CI doesn't fail and stuff can be merged. Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Vasily Khoruzhick <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2935>
* gitlab-ci/lava: add pipeline information in the lava job nameNeil Armstrong2020-01-211-0/+1
| | | | | | | | | | | In order to have more informations in the LAVA jobs list, add the current pipeline URL and commit ref name in the LAVA job name. Signed-off-by: Neil Armstrong <[email protected]> Reviewed-by: Tomeu Vizoso <[email protected]> Reviewed-by: Daniel Stone <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2337> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2337>
* ci: Re-enable CI for lima on mali450Vasily Khoruzhick2020-01-211-2/+5
| | | | | | | | | | | | | | | | Amend fails and skips lists basing on lists from Andreas Baierl, shard mali400 job across two devices since it takes close to 10min and rename jobs to lima-mali400-test and lima-mali450-test. Also don't set MESA_GLES_VERSION_OVERRIDE=3.0 for lima since we don't support GLES 3.0 and lower DEQP_PARALLEL to 3 for jobs on H3. Keep mali400 jobs disabled atm since they take too much time to complete and we also get some unexplicable failures in dEQP-GLES2.functional.default_vertex_attrib.* Signed-off-by: Vasily Khoruzhick <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3163> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3163>
* ci: lava: pass CI_NODE_INDEX and CI_NODE_TOTAL to lava jobsVasily Khoruzhick2020-01-211-1/+3
| | | | | | | | | | | deqp-runner.sh uses it to determine whether we split job across multiple devices and if we do what's the node index. With this change we now can set 'parallel: N' in job description if we want to split the job. Signed-off-by: Vasily Khoruzhick <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3163>
* gitlab-ci: Consolidate container and build stages for LAVATomeu Vizoso2020-01-141-146/+51
| | | | | | | | | | | | | | | | Use the normal build job to also prepare the artifacts for LAVA jobs. For that, the build container needs to also build the test suites, kernel, ramdisk, etc. Then the build job will place the just-built Mesa in the ramdisk and the test job can generate a LAVA job and point to those artifacts. Signed-off-by: Tomeu Vizoso <[email protected]> Acked-by: Alyssa Rosenzweig <[email protected]> Reviewed-by: Daniel Stone <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295>
* gitlab-ci: Upgrade kernel for LAVA jobs to v5.5-rc5Tomeu Vizoso2020-01-131-1/+1
| | | | | | | | Some fixes got in that should prevent hangs in lima jobs. Signed-off-by: Tomeu Vizoso <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3363> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3363>
* gitlab-ci: Switch LAVA jobs to use shared dEQP runnerTomeu Vizoso2020-01-061-2/+4
| | | | | | | | | | | | | Take one step towards sharing code between the LAVA and non-LAVA jobs, with the goals of reducing maintenance burden and use of computational resources. The env var DEQP_NO_SAVE_RESULTS allows us to skip the procesing of the XML result files, which can take a long time and is not useful in the LAVA case as we are not uploading artifacts anywhere at the moment. Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Eric Anholt <[email protected]>
* gitlab-ci: Update kernel for LAVA to 5.5-rc1 plus fixesTomeu Vizoso2020-01-061-1/+1
| | | | | Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Eric Anholt <[email protected]>
* ci: Remove T820 from CI temporarilyNeil Armstrong2019-12-171-1/+1
| | | | | | | | | | | Our lab will have continuous programmed power cuts until the 6th January 2020, so it's safer to disable the T820 CI running on the BayLibre kernelCI lab to avoid breaking CI. Signed-off-by: Neil Armstrong <[email protected]> Reviewed-by: Tomeu Vizoso <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3135> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3135>
* ci: Reinstate Panfrost CIAlyssa Rosenzweig2019-12-161-2/+2
| | | | | Signed-off-by: Alyssa Rosenzweig <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3118>
* ci: Remove T760/T860 from CI temporarilyAlyssa Rosenzweig2019-12-131-2/+2
| | | | | | | | | I feel really bad about this but this one test is flaking. I don't want to do a mass revert (and bisection is extremely difficult with nondeterministic/Heisenbugs), but it's Friday night and master needs to pass. This commit should be reverted asap (once the flake is solved) Signed-off-by: Alyssa Rosenzweig <[email protected]>
* gitlab-ci: Use lavacli from packagesRohan Garg2019-12-111-1/+1
| | | | | | | | | | lavacli 0.9.8 is now available in Debian Testing. Ref: https://tracker.debian.org/news/1066828/lavacli-098-1-migrated-to-testing/ Fixes: 555c0de ("gitlab-ci: Move LAVA-related files into top-level ci dir") Signed-off-by: Rohan Garg <[email protected]> Acked-by: Alyssa Rosenzweig <[email protected]> Reviewed-by: Tomeu Vizoso <[email protected]>
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-13 09:06:47 +0000