aboutsummaryrefslogtreecommitdiffstats
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* gitlab-ci: bump Vulkan CTS to 1.2.1.0Samuel Pitoiset2020-03-161-1/+1
| | | | | | | | | Vulkan CTS 1.1.6.0 is quite old. Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Eric Anholt <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4179> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4179>
* gitlab-ci: do not set the number of deqp-parallel jobs for RADV CTSSamuel Pitoiset2020-03-161-1/+0
| | | | | | | | Let's the runner uses the maximum number of jobs to speedup CTS. Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Eric Anholt <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4179>
* ci: Make a simple little bare-metal fastboot mode for db410c.Eric Anholt2020-03-111-4/+30
| | | | | | | | | | | | | | | | | 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: build RADV in meson-i386 to avoid 32-bit build failuresSamuel Pitoiset2020-03-111-3/+8
| | | | | | | Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Michel Dänzer <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4044> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4044>
* gitlab-ci: Don't restrict ppc64el/s390x build jobs to gstreamer runnersMichel Dänzer2020-03-111-2/+0
| | | | | | | | | The packet runners have beefier CPUs now and don't seem to run into test timeouts anymore. Reviewed-by: Daniel Stone <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4128> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4128>
* gitlab-ci: Remove unneeded python3-pilkit dependencyAndres Gomez2020-03-111-1/+1
| | | | | | | | It was added with tracie, but it doesn't depend on it. Signed-off-by: Andres Gomez <[email protected]> Reviewed-by: Eric Engestrom <[email protected]> Reviewed-by: Samuel Pitoiset <[email protected]>
* gitlab-ci: add rules:changes for RADVSamuel Pitoiset2020-03-111-0/+1
| | | | | | | | | | Including mesa_core_file_list is probably not the best but it's better than nothing. Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Bas Nieuwenhuizen <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4117> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4117>
* gitlab-ci: rules:changes to test on tested drivers changesPierre-Eric Pelloux-Prayer2020-03-091-8/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-2/+4
| | | | | | | | | | | | | 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: add a job that runs Fossilize on RADV/Polaris10Samuel Pitoiset2020-03-051-2/+15
| | | | | | | | | | | | | | RADV_FORCE_FAMILY forces creating a null device that allows RADV to be instanced without AMDGPU. The Fossilize database only contains pipelines from the Sascha Vulkan triangle demos at the moment. I will add more once this is merged. Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Michel Dänzer <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3960> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3960>
* gitlab-ci: enable building the test image for VK unconditionallySamuel Pitoiset2020-03-051-15/+2
| | | | | | | | | | | | | | It was diabled because RADV is the only driver that tests Vulkan and running CTS on my personal machine and without recovery is not safe enough for CI (too long and too unstable). Now that we are going to test Fossilize with RADV, it's needed to build the test image for VK unconditionally. As RADV now supports creating NULL devices, the fossilize jobs can run everywhere. Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Michel Dänzer <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3960>
* gitlab-ci: add Fossilize support to detect compiler regressionsSamuel Pitoiset2020-03-051-0/+5
| | | | | | | | | Fossilize is equivalent to vkpipeline-db but it's definitely more robust. This is based on the CI traces system. Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Alexandros Frantzis <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3960>
* gitlab-ci: build Fossilize in the test image for VKSamuel Pitoiset2020-03-051-1/+1
| | | | | | Signed-off-by: Samuel Pitoiset <[email protected]> Reviewed-by: Michel Dänzer <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3960>
* gitlab-ci: Distribute jobs across more stagesMichel Dänzer2020-03-051-4/+19
| | | | | | | | | | | | | | 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>
* gitlab-ci: Drop "test-" prefix from llvmpipe/softpipe job namesMichel Dänzer2020-03-051-7/+7
| | | | | | | | Redundant. Reviewed-by: Pierre-Eric Pelloux-Prayer <[email protected]> Reviewed-by: Eric Engestrom <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3995>
* gitlab-ci: Add jobs to be able to test VulkanAndres Gomez2020-03-041-4/+24
| | | | | | | | Also, adds an example job for radv. Signed-off-by: Andres Gomez <[email protected]> Reviewed-by: Samuel Pitoiset <[email protected]> Reviewed-by: Alexandros Frantzis <[email protected]>
* gitlab-ci: Add gfxreconstruct traces supportAndres Gomez2020-03-041-1/+1
| | | | | | Signed-off-by: Andres Gomez <[email protected]> Reviewed-by: Samuel Pitoiset <[email protected]> Reviewed-by: Alexandros Frantzis <[email protected]>
* gitlab-ci: Change devices format to <api-vendor-deviceId>Andres Gomez2020-03-041-1/+1
| | | | | | | | | | | In preparation to having "vk" (Vulkan) along "gl" (OpenGL/ES). This is so it is clearer which traces belong to which API and also for the build jobs. Signed-off-by: Andres Gomez <[email protected]> Reviewed-by: Samuel Pitoiset <[email protected]> Reviewed-by: Alexandros Frantzis <[email protected]>
* gitlab-ci: build VulkanTools into the Vulkan testing containerAndres Gomez2020-03-041-1/+1
| | | | | | | | In preparation for having automated testing with Vulkan traces. Signed-off-by: Andres Gomez <[email protected]> Reviewed-by: Samuel Pitoiset <[email protected]> Reviewed-by: Alexandros Frantzis <[email protected]>
* gitlab-ci: build gfxreconstruct into the Vulkan testing containerAndres Gomez2020-03-041-1/+1
| | | | | | | | In preparation for having automated testing with Vulkan traces. Signed-off-by: Andres Gomez <[email protected]> Reviewed-by: Samuel Pitoiset <[email protected]> Reviewed-by: Alexandros Frantzis <[email protected]>
* gitlab-ci: add missing popd to the build-deqp-vk.sh scriptAndres Gomez2020-03-041-1/+1
| | | | | | | | | Since we are at it, replace "cd" with pushd / popd and homogenize how VK-GL-CTS is built in comparison with other build scripts. Signed-off-by: Andres Gomez <[email protected]> Reviewed-by: Samuel Pitoiset <[email protected]> Reviewed-by: Alexandros Frantzis <[email protected]>
* ci: Flip db410c back to docker mode.Eric Anholt2020-03-031-0/+8
| | | | | | | | | | 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: Switch testing on db410c over to LAVA.Eric Anholt2020-03-021-8/+0
| | | | | | | | | | | | | | | | | | | 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>
* ci: Enable -Werror on meson-vulkan and meson-testing.Eric Anholt2020-02-271-0/+3
| | | | | | | | | | | | | | | I want to make sure that I don't introduce warnings in turnip where we have active work going on, and I also want to make sure that the drivers we care about testing are warnings-clean. As with the previous -Werror change, this is for CI only and doesn't affect end-user builds. Reviewed-by: Michel Dänzer <[email protected]> Reviewed-by: Eric Engestrom <[email protected]> Reviewed-by: Samuel Pitoiset <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3607> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3607>
* ci: Include db410c support in the ARM container.Eric Anholt2020-02-271-1/+1
| | | | | | | | | | | | | | | | | | | | | | I'm working on moving the db410c CI from docker to LAVA, which means we get to boot a custom kernel. To do that, we need to enable ARCH_QCOM in the kernel, save the dtb around, and include abootimg in our container so that we can generate combined kernel/dtb/ramdisk images for fastboot. LAVA's fastboot support is unable to pack the overlay into an abootimg image, just a cpio rootfs. We could flash the cpio rootfs after overlay addition, but that takes 2 minutes to do, and causes wear on the devices. Instead, we'll bring up the network at boot and use wget to fetch the overlay. We'll want network support anyway, so that we can transfer the failure xmls back to the gitlab job's artifacts at some point. Since the msm GPU and realtek network firmware increase our payload by 3MB, add in firmware compression so that it doesn't waste as much RAM on devices not using it. Reviewed-by: Tomeu Vizoso <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3928> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3928>
* ci: Remove LLVM from ARM test drivers.Eric Anholt2020-02-271-0/+4
| | | | | | | | | | | | | The LLVM libraries were a significant fraction of the entire payload (55M/250M uncompressed) into the initramfs of the test boards, but LLVM is only used for the draw module used in select/feedback (which isn't even tested in CI on ARM yet). Assume that llvmpipe draw is safe enough for ARM given the coverage on x86, and disable LLVM for these jobs. Reviewed-by: Tomeu Vizoso <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3928>
* ci: Split out radv build-testing on arm64Rohan Garg2020-02-271-1/+10
| | | | | | | | | | | | radv needs libllvm which increases our ramdisk size significantly. Since this driver is only build tested, we can split it out into a separate job. Signed-off-by: Rohan Garg <[email protected]> Reviewed-by: Samuel Pitoiset <[email protected]> Reviewed-by: Eric Anholt <[email protected]> Reviewed-by: Tomeu Vizoso <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3928>
* gitlab-ci: Move to 5.5 kernel plus fixes for PanfrostTomeu Vizoso2020-02-261-1/+1
| | | | | | | | | | There's two fixes that help with stability when running dEQP on Kevin Chromebooks. Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Alyssa Rosenzweig <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3876> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3876>
* ci: Make sure that we have a proper shell prompt for LAVA.Eric Anholt2020-02-211-1/+1
| | | | | | | | | | | | | LAVA finds a '#' early in boot and races to emit its shell commands. Apparently for the current boards those serial commands end up getting buffered such that things work out, but for db410c and db820c, the buffer is lost and LAVA gets stuck waiting for the prompt. By setting a prompt, we can delay our commands until we're actually supposed to emit them (and suppress a complaint from the lava dispatcher that we're using a risky prompt!) Reviewed-by: Tomeu Vizoso <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3883>
* gitlab-ci: Automated testing with OpenGL tracesAlexandros Frantzis2020-02-201-1/+18
| | | | | | | | | | | | | | Introduce automated testing of Mesa by replaying traces with Renderdoc or Apitrace. For now only LLVMPipe is tested, but other drivers can be tested if there's runners with the necessary hardware. Signed-off-by: Alexandros Frantzis <[email protected]> Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Eric Anholt <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2935> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2935>
* ci: bump debian image and change llvm deps to 8Dave Airlie2020-02-151-3/+1
| | | | | | | | | v3: remove version in a few places (Michel) Reviewed-by: Michel Dänzer <[email protected]> Reviewed-by: Adam Jackson <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3805> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3805>
* Revert "gitlab-ci: disable a630 tests as mesa-cheza is down (again)"Fritz Koenig2020-02-131-6/+6
| | | | | | | This reverts commit 18657c0c0a9074d3dfc0763b396929bcf34f71b4 Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3804> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3804>
* gitlab-ci: Only use gstreamer runners for the s390x job for nowMichel Dänzer2020-02-111-0/+2
| | | | | | | | | | | | | The fdo-packet-* runners keep hitting the (already quite long) timeouts for some of the tests, taking many times as long for them as the gstreamer runners. The fdo-gitlab-gce-runner3 runner would work as well, but it doesn't have any tags we could use. Acked-by: Daniel Stone <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3760> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3760>
* gitlab-ci: disable a630 tests as mesa-cheza is down (again)Samuel Pitoiset2020-02-101-6/+6
| | | | | | Signed-off-by: Samuel Pitoiset <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3758> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3758>
* ci: Drop turnip opt-in optionKristian H. Kristensen2020-02-071-2/+0
| | | | | Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3742> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3742>
* ci: Bump the GLES CTS version to 3.2.6.1.Eric Anholt2020-02-061-3/+3
| | | | | | | | | | 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 <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3662> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3662>
* gitlab-ci: Build radeonsi & RADV in the ppc64el jobMichel Dänzer2020-02-051-1/+2
| | | | | | | | | This requires cross-building libdrm for ppc64el. Reviewed-by: Adam Jackson <[email protected]> Reviewed-by: Eric Anholt <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3643> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3643>
* gitlab-ci: Add ppc64el and s390x cross-build jobsMichel Dänzer2020-02-051-2/+21
| | | | | | | | | | | | | Using LLVM 8 for ppc64el and 7 for s390x (which hits some coroutine related issues with LLVM 8). There are some test failures we need to ignore for now. Also, the timeout needs to be bumped from the default 30s for some tests, because they can take longer under emulation. Reviewed-by: Adam Jackson <[email protected]> Reviewed-by: Eric Anholt <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3643>
* gitlab-ci: Update to latest ci-templates HEADMichel Dänzer2020-02-051-2/+1
| | | | | | | | | | | | | Among other things, this increases robustness when copying a docker image from the main Mesa project to a forked project, avoiding spurious image rebuilds from scratch. Also drop the comment about .gitlab-ci/lava-gitlab-ci.yml, it doesn't include the templates anymore. Reviewed-by: Adam Jackson <[email protected]> Reviewed-by: Eric Anholt <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3643>
* gitlab-ci: Switch kernel for LAVA jobs to 5.5Tomeu Vizoso2020-02-041-1/+1
| | | | | | | | | All fixes we were carrying in our branch have been merged already. Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Alyssa Rosenzweig <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3692> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3692>
* Revert "gitlab-ci: disable a630 tests as mesa-cheza is down"Fritz Koenig2020-02-031-6/+6
| | | | | | | This reverts commit f38851d84c583b1c62ea95edbc42eb5e2ad14fa8 Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3687> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3687>
* gitlab-ci: disable a630 tests as mesa-cheza is downEric Engestrom2020-02-031-6/+6
| | | | | | Signed-off-by: Eric Engestrom <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3677> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3677>
* ci: Enable -Werror on the meson-i386 build.Eric Anholt2020-01-281-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | I find warnings to be very disruptive to my workflow (using emacs's "go to next error" feature), and I periodically have to go clean up other people's drivers to get back to finding my own warnings in the noise. I know I'm not the only one doing something like this. We don't want to enable -Werror by default in builds, since it means that end users will have builds spuriously fail based on what compiler version and opt flags they have compared to what the devs are using. However, it is quite easy to have CI ensure that we at least don't introduce warnings on the compiler version that it uses. For now I've just enabled it on meson-i386 to cover a bunch of Mesa core and get us started on ratcheting up warnings-cleanliness in the tree, without me having to fix up all the drivers at once. Reviewed-by: Daniel Stone <[email protected]> Reviewed-by: Kristian H. Kristensen <[email protected]> Reviewed-by: Alyssa Rosenzweig <[email protected]> Reviewed-by: Eric Engestrom <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3539> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3539>
* gitlab-ci: Use single if for manual job rules entryMichel Dänzer2020-01-221-2/+1
| | | | | | | | | | | | I thought multiple ifs would all need to match, but looks like only the last one (or either one?) does. This should prevent a manual pipeline from getting created after merging changes which can't affect the pipeline. Reviewed-by: Eric Engestrom <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3474> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3474>
* gitlab-ci: Set GIT_STRATEGY to none for the dummy jobMichel Dänzer2020-01-221-0/+2
| | | | | | | It doesn't need anything from the Git repository. Reviewed-by: Eric Engestrom <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3474>
* gitlab-ci: Skip ext_timer_query/time-elapsedMatt Turner2020-01-221-0/+1
| | | | | | | | | This test's result is unpredictable, so it may occasionally pass when we expect it to fail, thus causing the CI pipeline to fail. Reviewed-by: Eric Anholt <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3498> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3498>
* gitlab-ci: Stop using manual jobs for merge requestsMichel Dänzer2020-01-151-27/+45
| | | | | | | | | | | | | | | | | | | | | | | They were causing trouble with Marge Bot: The project settings require that the pipeline succeeds before a merge request (MR) can be merged, otherwise Marge doesn't wait for the pipeline to succeed before merging an MR assigned to her. But Marge can't start manual jobs, so she would always time out waiting for pipelines with manual jobs. To avoid this, use these rules: * Run the pipeline by default for MRs and main project branches changing any files affecting it. * For other MRs, run a single dummy job which always succeeds. * Don't run any jobs for main project branch changes (e.g. from an MR having been merged) not affecting the pipeline. * Allow jobs to be started manually on branches of forked projects, as before. Acked-by: Pierre-Eric Pelloux-Prayer <[email protected]> Acked-by: Daniel Stone <[email protected]> Reviewed-by: Eric Engestrom <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3361> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3361>
* gitlab-ci: Consolidate container and build stages for LAVATomeu Vizoso2020-01-141-9/+12
| | | | | | | | | | | | | | | | 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: Test against LLVM / clang 9 on x86Michel Dänzer2020-01-071-8/+9
| | | | | | | | They're not available for Debian buster yet, so we have to use upstream snapshot packages again. In contrast to earlier, we now store the LLVM APT repository key in Git instead of re-downloading it every time.
* gitlab-ci: Switch LAVA jobs to use shared dEQP runnerTomeu Vizoso2020-01-061-3/+3
| | | | | | | | | | | | | 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]>
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-14 05:59:53 +0000