From: Rob Clark <robdclark@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: Emma Anholt <emma@anholt.net>,
Helen Koike <helen.koike@collabora.com>,
Rob Clark <robdclark@chromium.org>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH] drm/ci: Default to UART for logging
Date: Fri, 6 Oct 2023 10:32:04 -0700 [thread overview]
Message-ID: <20231006173205.371205-1-robdclark@gmail.com> (raw)
From: Rob Clark <robdclark@chromium.org>
ssh logging is the default for mesa, as it is generally more reliable.
But if there are kernel issues, especially at boot, UART logging is
infinitely more useful.
Signed-off-by: Rob Clark <robdclark@chromium.org>
---
drivers/gpu/drm/ci/gitlab-ci.yml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/gpu/drm/ci/gitlab-ci.yml b/drivers/gpu/drm/ci/gitlab-ci.yml
index 2c4df53f5dfe..7c55f02f7313 100644
--- a/drivers/gpu/drm/ci/gitlab-ci.yml
+++ b/drivers/gpu/drm/ci/gitlab-ci.yml
@@ -27,6 +27,12 @@ variables:
LAVA_JOB_PRIORITY: 30
+ # Default to UART logging. Mesa uses ssh by default, as that is more
+ # reliable if you have a stable kernel. But kernel CI is more likely
+ # to encounter unstable kernels (and has lower volume of CI jobs so is
+ # less likely to be troubled by occasional UART flakes)
+ LAVA_FORCE_UART: 1
+
default:
before_script:
- export SCRIPTS_DIR=$(mktemp -d)
--
2.41.0
next reply other threads:[~2023-10-06 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 17:32 Rob Clark [this message]
2023-10-09 11:19 ` [PATCH] drm/ci: Default to UART for logging Helen Koike
2023-10-13 16:28 ` Daniel Stone
2023-10-13 18:14 ` Rob Clark
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=20231006173205.371205-1-robdclark@gmail.com \
--to=robdclark@gmail.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emma@anholt.net \
--cc=helen.koike@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.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