All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Edwin Török" <edwin.torok@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: "Edwin Török" <edwin.torok@citrix.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	"Michal Orzel" <michal.orzel@amd.com>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Julien Grall" <julien@xen.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Doug Goldstein" <cardoe@cardoe.com>
Subject: [PATCH v1 0/5] run unit tests in the CI
Date: Mon, 30 Mar 2026 17:17:23 +0100	[thread overview]
Message-ID: <cover.1774886602.git.edwin.torok@citrix.com> (raw)

Currently the unit tests aren't run in the CI during the build.
Introduce a 'make check' rule that can run them all (in parallel if `-j`
is specified).

To make reading the CI output easier make's `-O` flag is used (which
buffers output per target, making it obvious which command failed).

TBD: what is the actual minimum version of binutils required by the
existing tests, because Ubuntu 16.04 with binutil 2.26.1 failed.
That version of Ubuntu is EoL in a few days, so it is dropped from the CI build step.
The actual containers and the xilinx-arm64 jobs are kept for now
(although these should be updated to use bionic).

A followup patch series will rearrange the unit test make rules,
so it is useful to test that all the unit tests worked both prior and
following that change on all supported platforms in the CI.

For convenience this series is also available as a git repository:
https://gitlab.com/xen-project/people/edwintorok/xen/-/tree/private/edvint/run-ci?ref_type=heads

Edwin Török (5):
  README: update minimum make to 4.1
  CI: drop Ubuntu 16.04
  tools/test: introduce a 'make check' rule
  automation/scripts/build: run unit tests in the CI
  automation/scripts/build: group command output from parallel jobs

 Makefile                        |  4 ++++
 README                          |  2 +-
 automation/gitlab-ci/build.yaml | 10 ----------
 automation/scripts/build        | 10 ++++++----
 tools/Makefile                  |  4 ++++
 tools/Rules.mk                  |  2 +-
 tools/tests/Makefile            | 20 +++++++++++++++++++-
 7 files changed, 35 insertions(+), 17 deletions(-)

-- 
2.47.3



             reply	other threads:[~2026-03-30 16:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 16:17 Edwin Török [this message]
2026-03-30 16:17 ` [PATCH v1 1/5] README: update minimum make to 4.1 Edwin Török
2026-03-31  6:14   ` Jan Beulich
2026-03-31  8:15     ` Edwin Torok
2026-03-31  8:24       ` Jan Beulich
2026-03-31 18:53         ` Edwin Torok
2026-03-30 16:17 ` [PATCH v1 2/5] CI: drop Ubuntu 16.04 Edwin Török
2026-03-31  6:58   ` Jan Beulich
2026-03-31  8:29     ` Edwin Torok
2026-03-31  9:01       ` Jan Beulich
2026-03-30 16:17 ` [PATCH v1 3/5] tools/test: introduce a 'make check' rule Edwin Török
2026-03-31  7:13   ` Jan Beulich
2026-03-30 16:17 ` [PATCH v1 4/5] automation/scripts/build: run unit tests in the CI Edwin Török
2026-03-30 16:17 ` [PATCH v1 5/5] automation/scripts/build: group command output from parallel jobs Edwin Török

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=cover.1774886602.git.edwin.torok@citrix.com \
    --to=edwin.torok@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=cardoe@cardoe.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.