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 v2 6/6] gitlab: greatly expand captured info about CI runner environment
Date: Wed, 24 Jun 2026 13:46:57 +0100	[thread overview]
Message-ID: <20260624124657.2725376-7-berrange@redhat.com> (raw)
In-Reply-To: <20260624124657.2725376-1-berrange@redhat.com>

To aid in debugging wierd CI failures we need greater information
about the CI runner environment. It is usually container based
and can have some unexpected characteristics that significantly
differ from a developer's local environment.

This captures the mount list, CPU model, memory information,
device node lists, kernel info, user identity and all environment
variables.

Since this information can get quite large it is not emitted
directly in the logs, rather it is exposed in job artifacts
under the "ci-runner-env" directory.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---
 .gitlab-ci.d/base.yml               | 11 ++++++++++-
 .gitlab-ci.d/buildtest-template.yml |  2 ++
 2 files changed, 12 insertions(+), 1 deletion(-)

diff --git a/.gitlab-ci.d/base.yml b/.gitlab-ci.d/base.yml
index a75fb37d61..bec04138fa 100644
--- a/.gitlab-ci.d/base.yml
+++ b/.gitlab-ci.d/base.yml
@@ -141,6 +141,7 @@ variables:
     expire_in: 7 days
     paths:
       - build/meson-logs
+      - ci-runner-env
     reports:
       junit: build/meson-logs/*.junit.xml
   before_script:
@@ -150,7 +151,15 @@ variables:
     # Prevent logs (if any) from prior build job artifacts
     # from being duplicated in the new job artifacts
     - rm -f build/meson-logs/*
-    - test -f /packages.txt && cat /packages.txt
+    - mkdir -p ci-runner-env
+    - test -f /packages.txt && cp /packages.txt ci-runner-env/packages.txt
+    - cp /proc/mounts ci-runner-env/mounts.txt
+    - cp /proc/cpuinfo ci-runner-env/cpuinfo.txt
+    - cp /proc/meminfo ci-runner-env/meminfo.txt
+    - ls -l /dev > ci-runner-env/devices.txt
+    - uname -a > ci-runner-env/kernel.txt
+    - id -a > ci-runner-env/user.txt
+    - printenv | sort > ci-runner-env/environ.txt
     - section_end setup
 
 .base_meson_ccache_job_template:
diff --git a/.gitlab-ci.d/buildtest-template.yml b/.gitlab-ci.d/buildtest-template.yml
index 11d7a75667..e62b3f2123 100644
--- a/.gitlab-ci.d/buildtest-template.yml
+++ b/.gitlab-ci.d/buildtest-template.yml
@@ -38,6 +38,7 @@
     paths:
       - build
       - .git-submodule-status
+      - ci-runner-env
     exclude:
       - build/**/*.p
       - build/**/*.a.p
@@ -83,6 +84,7 @@
     paths:
       - build/meson-logs
       - build/tests/functional/*/*/*.log
+      - ci-runner-env
     reports:
       junit: build/meson-logs/*.junit.xml
   after_script:
-- 
2.54.0



  parent reply	other threads:[~2026-06-24 12:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-24 12:46 [PATCH v2 0/6] gitlab: expose more info about CI runner environment as artifacts Daniel P. Berrangé
2026-06-24 12:46 ` [PATCH v2 1/6] gitlab: remove unused .cross_test_artifacts template Daniel P. Berrangé
2026-06-24 13:03   ` Philippe Mathieu-Daudé
2026-06-24 16:56   ` Pierrick Bouvier
2026-06-24 12:46 ` [PATCH v2 2/6] gitlab: move .meson_job_template into base.yaml Daniel P. Berrangé
2026-06-24 16:56   ` Pierrick Bouvier
2026-06-24 12:46 ` [PATCH v2 3/6] gitlab: use .base_meson_job_template from crossbuild jobs Daniel P. Berrangé
2026-06-24 16:56   ` Pierrick Bouvier
2026-06-24 12:46 ` [PATCH v2 4/6] gitlab: pull ccache setup into .base_meson_ccache_job_template Daniel P. Berrangé
2026-06-24 16:57   ` Pierrick Bouvier
2026-06-24 12:46 ` [PATCH v2 5/6] gitlab: pull before_script logic into .base_meson_job_template Daniel P. Berrangé
2026-06-24 16:58   ` Pierrick Bouvier
2026-06-24 12:46 ` Daniel P. Berrangé [this message]
2026-06-24 16:58   ` [PATCH v2 6/6] gitlab: greatly expand captured info about CI runner environment Pierrick Bouvier

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=20260624124657.2725376-7-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.