[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAF6AEGtS8ZTiDs=6P4fkq9WjxAHbi6Nzr2vNVqiF-JaMqGYqgQ@mail.gmail.com>
Date: Fri, 13 Oct 2023 11:14:02 -0700
From: Rob Clark <robdclark@...il.com>
To: Daniel Stone <daniel@...ishbar.org>
Cc: dri-devel@...ts.freedesktop.org,
Rob Clark <robdclark@...omium.org>,
Emma Anholt <emma@...olt.net>,
open list <linux-kernel@...r.kernel.org>,
Helen Koike <helen.koike@...labora.com>
Subject: Re: [PATCH] drm/ci: Default to UART for logging
On Fri, Oct 13, 2023 at 9:28 AM Daniel Stone <daniel@...ishbar.org> wrote:
>
> On Fri, 6 Oct 2023 at 18:32, Rob Clark <robdclark@...il.com> wrote:
> > 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.
>
> Hmm, we should still be capturing the UART boot logs regardless. Those
> go into a collapsed 'LAVA boot' section but they don't just disappear
> ... ?
Hmm, I wasn't seeing anything in the raw log, which doesn't collapse sections..
That said, I still think uart is preferable to ssh for kernel CI.. we
aren't running jobs at the scale of mesa CI jobs so even if we get
UART flakes 1/1000 (or even 1/100) times, that is an acceptable
trade-off for the fact that uart can still work when things are too
fubar for ssh.
BR,
-R
Powered by blists - more mailing lists