aboutsummaryrefslogtreecommitdiffstats
path: root/.gitlab-ci/lava-deqp.yml.jinja2
Commit message (Collapse)AuthorAgeFilesLines
* gitlab-ci: More stable URL for kernel and ramdisk artifacts, for LAVATomeu Vizoso2020-07-071-9/+6
| | | | | | | | | | | | | | | | | | | | | 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: Enable --compact-display false on all dEQP runs.Eric Anholt2020-04-271-1/+1
| | | | | | | | We always want to see status updates happening in the logs, otherwise it can like maybe your machine hung until the run actually completes. Reviewed-by: Tomeu Vizoso <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4621>
* gitlab-ci: Place files from the Mesa repo into the build tarballTomeu Vizoso2020-03-261-9/+4
| | | | | | | | | | | | | | | | | | There's some files from the .gitlab-ci directory that are needed in the test stage and that, because the Mesa repository isn't checked out in that stage, need to be made available through other means. Because those files are going to be needed in LAVA devices, place them ino the tarball containing the built files so it's available to both gitlab-ci runners and LAVA devices. Before those files were passed in the artifacts of the Gitlab CI job, but this commit places them into the built tarball so scripts later in the pipeline don't need to account for this discrepancy. Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Eric Anholt <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4295>
* gitlab-ci/lava: fix handling of lava tagsNeil Armstrong2020-03-161-1/+2
| | | | | | | | | | | | | | | | | | | | | | | The lava tags was a python array not it's a gitlab CI string, slit the string with periods in the jinja2 template to avoid having the following tags : tags: - p - a - n - f - r - o - s - t instead of : tags: - panfrost Signed-off-by: Neil Armstrong <[email protected]> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4057>
* ci: Switch testing on db410c over to LAVA.Eric Anholt2020-03-021-1/+19
| | | | | | | | | | | | | | | | | | | 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>
* gitlab-ci: Run GLES3 tests in dEQP on PanfrostTomeu Vizoso2020-02-261-3/+1
| | | | | | | | | | 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>
* 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/lava: add pipeline information in the lava job nameNeil Armstrong2020-01-211-1/+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: lava: pass CI_NODE_INDEX and CI_NODE_TOTAL to lava jobsVasily Khoruzhick2020-01-211-0/+2
| | | | | | | | | | | 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-5/+9
| | | | | | | | | | | | | | | | 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: Switch LAVA jobs to use shared dEQP runnerTomeu Vizoso2020-01-061-2/+23
| | | | | | | | | | | | | 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]>
* Add support for T820 CI JobsNeil Armstrong2019-12-031-0/+6
| | | | | | | Tomeu: - Small rebase fixups Signed-off-by: Neil Armstrong <[email protected]> Signed-off-by: Tomeu Vizoso <[email protected]>
* 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]>
* gitlab-ci/lava: Test Lima driver with dEQPTomeu Vizoso2019-10-101-5/+6
| | | | | | | | | | | | Run dEQP on boards with Mali 400 and 450 in Baylibre's lab. There's lots of skipped tests because of crashes and undetermined behavior. May be a good idea to run the tests with valgrind and fix any issues found. Signed-off-by: Tomeu Vizoso <[email protected]> Reviewed-by: Vasily Khoruzhick <[email protected]> Reviewed-by: Neil Armstrong <[email protected]>
* gitlab-ci: Move LAVA-related files into top-level ci dirTomeu Vizoso2019-10-061-0/+60
In preparation for testing drivers other than Panfrost in LAVA labs. 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-21 07:18:41 +0000