All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH] gitlab: capture filesystem, CPU, memory and kernel info in logs
Date: Thu, 21 May 2026 11:36:24 +0100	[thread overview]
Message-ID: <20260521103624.1645809-1-berrange@redhat.com> (raw)

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(+)

diff --git a/.gitlab-ci.d/buildtest-template.yml b/.gitlab-ci.d/buildtest-template.yml
index 005058625e..005f49702b 100644
--- a/.gitlab-ci.d/buildtest-template.yml
+++ b/.gitlab-ci.d/buildtest-template.yml
@@ -27,6 +27,10 @@
     - section_start setup "Pre-script setup"
     - JOBS=$(expr $(nproc) + 1)
     - cat /packages.txt
+    - cat /proc/mounts
+    - cat /proc/cpuinfo
+    - cat /proc/meminfo
+    - uname -a
     - section_end setup
   script:
     - export CCACHE_BASEDIR="$(pwd)"
@@ -102,6 +106,10 @@
     # Prevent logs from the build job that run earlier
     # from being duplicated in the test job artifacts
     - rm -f build/meson-logs/*
+    - cat /proc/mounts
+    - cat /proc/cpuinfo
+    - cat /proc/meminfo
+    - uname -a
 
 
 .functional_test_job_template:
@@ -126,6 +134,10 @@
     # Prevent logs from the build job that run earlier
     # from being duplicated in the test job artifacts
     - rm -f build/meson-logs/*
+    - cat /proc/mounts
+    - cat /proc/cpuinfo
+    - cat /proc/meminfo
+    - uname -a
   after_script:
     - cd build
     - du -chs ${CI_PROJECT_DIR}/*-cache
-- 
2.54.0



             reply	other threads:[~2026-05-21 10:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21 10:36 Daniel P. Berrangé [this message]
2026-05-21 13:25 ` [PATCH] gitlab: capture filesystem, CPU, memory and kernel info in logs Pierrick Bouvier
2026-06-24 12:44   ` Daniel P. Berrangé

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=20260521103624.1645809-1-berrange@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.