From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] gitlab: capture filesystem, CPU, memory and kernel info in logs
Date: Wed, 24 Jun 2026 13:44:22 +0100 [thread overview]
Message-ID: <ajvRJu-1VAk88R1c@redhat.com> (raw)
In-Reply-To: <96a48300-ec95-4291-8cb8-439d255de9aa@oss.qualcomm.com>
On Thu, May 21, 2026 at 08:25:12AM -0500, Pierrick Bouvier wrote:
> On 5/21/2026 5:36 AM, Daniel P. Berrangé wrote:
> > For tests we have often had wierd failures that are related to the
> > runner environment. For example, tests that fail only with specific
> > filesystem setups.
> >
> > Since we don't control the runners directly, it is important to
> > capture info about the environment to aid in failure diagnosis.
> >
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > .gitlab-ci.d/buildtest-template.yml | 12 ++++++++++++
> > 1 file changed, 12 insertions(+)
> >
>
> Good idea,
> Reviewed-by: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>
>
> Maybe add a ls -al /dev and id -a, to sort out potential right issues to
> access devices?
Yes, revisiting this, I'm adding those and doing many other changes
to improve consistency & maintainability. v2 incoming...
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
prev parent reply other threads:[~2026-06-24 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 10:36 [PATCH] gitlab: capture filesystem, CPU, memory and kernel info in logs Daniel P. Berrangé
2026-05-21 13:25 ` Pierrick Bouvier
2026-06-24 12:44 ` Daniel P. Berrangé [this message]
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=ajvRJu-1VAk88R1c@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.