From: Vignesh Raman <vignesh.raman@collabora.com>
To: helen.koike@collabora.com, airlied@gmail.com, daniel@ffwll.ch
Cc: david.heidelberg@collabora.com, sergi.blanch.torne@collabora.com,
guilherme.gallo@collabora.com, daniels@collabora.com,
gustavo.padovan@collabora.com, emma@anholt.net,
robdclark@gmail.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
virtualization@lists.linux-foundation.org,
linux-rockchip@lists.infradead.org,
linux-arm-msm@vger.kernel.org
Subject: [PATCH v6 07/10] drm: ci: virtio: Make artifacts available
Date: Wed, 29 Nov 2023 17:48:38 +0530 [thread overview]
Message-ID: <20231129121841.253223-8-vignesh.raman@collabora.com> (raw)
In-Reply-To: <20231129121841.253223-1-vignesh.raman@collabora.com>
There were no artifacts available for virtio job.
So make the artifacts available in the pipeline job.
Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>
---
v5:
- Added a new patch in the series to make artifacts available for virtio jobs
v6:
- No changes
---
drivers/gpu/drm/ci/test.yml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/ci/test.yml b/drivers/gpu/drm/ci/test.yml
index e0fdc55c9b69..2c9a1838e728 100644
--- a/drivers/gpu/drm/ci/test.yml
+++ b/drivers/gpu/drm/ci/test.yml
@@ -329,6 +329,8 @@ virtio_gpu:none:
script:
- ln -sf $CI_PROJECT_DIR/install /install
- mv install/bzImage /lava-files/bzImage
+ - mkdir -p $CI_PROJECT_DIR/results
+ - ln -sf $CI_PROJECT_DIR/results /results
- install/crosvm-runner.sh install/igt_runner.sh
needs:
- debian/x86_64_test-gl
--
2.40.1
next prev parent reply other threads:[~2023-11-29 12:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 12:18 [PATCH v6 00/10] drm: ci: fixes Vignesh Raman
2023-11-29 12:18 ` [PATCH v6 01/10] drm: ci: igt_runner: Remove todo Vignesh Raman
2023-11-29 12:18 ` [PATCH v6 02/10] drm: ci: Force db410c to host mode Vignesh Raman
2023-11-29 12:18 ` [PATCH v6 03/10] drm: ci: arm64.config: Enable DA9211 regulator Vignesh Raman
2023-11-29 12:18 ` [PATCH v6 04/10] drm: ci: Enable new jobs Vignesh Raman
2023-11-29 12:18 ` [PATCH v6 05/10] drm: ci: Use scripts/config to enable/disable configs Vignesh Raman
2023-11-29 12:18 ` [PATCH v6 06/10] drm: ci: mediatek: Set IGT_FORCE_DRIVER for mt8173 Vignesh Raman
2023-11-29 13:22 ` Daniel Stone
2023-11-30 13:50 ` Vignesh Raman
2023-12-05 17:58 ` Helen Koike
2023-11-29 12:18 ` Vignesh Raman [this message]
2023-12-05 18:00 ` [PATCH v6 07/10] drm: ci: virtio: Make artifacts available Helen Koike
2023-11-29 12:18 ` [PATCH v6 08/10] drm: ci: uprev IGT Vignesh Raman
2023-12-05 18:00 ` Helen Koike
2023-11-29 12:18 ` [PATCH v6 09/10] drm/doc: ci: Add IGT version details for flaky tests Vignesh Raman
2023-12-05 18:01 ` Helen Koike
2023-11-29 12:18 ` [PATCH v6 10/10] drm: ci: Update xfails Vignesh Raman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231129121841.253223-8-vignesh.raman@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=daniels@collabora.com \
--cc=david.heidelberg@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emma@anholt.net \
--cc=guilherme.gallo@collabora.com \
--cc=gustavo.padovan@collabora.com \
--cc=helen.koike@collabora.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robdclark@gmail.com \
--cc=sergi.blanch.torne@collabora.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).