mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Jules Maselbas <jmaselbas@zdiv.net>, jre@pengutronix.de
Subject: [PATCH 0/6] ci: run tests and static analysis on allyesconfig
Date: Wed, 26 Mar 2025 08:59:13 +0100	[thread overview]
Message-ID: <20250326075919.3448789-1-a.fatoum@pengutronix.de> (raw)

With a one-liner fix remaining[1], sandbox now builds allyesconfig sans
SDL/libftdi to completion. Let's seize the opportunity and add it to CI,
so we easily detect breakage around allyesconfig in future.

This series also switches the recently added Coverity and CodeQL Github
Actions to use allyesconfig to extend coverage to non-sandbox related
drivers as well.

[1]: https://lore.barebox.org/barebox/20250312-rpmb-v1-7-0f213382a3f3@pengutronix.de/T/#m4e6fcf916dd9461bbef25a93439ad8fdb36c8217

Ahmad Fatoum (6):
  sandbox: use CROSS_PKG_CONFIG when compiling sandbox arch code
  sandbox: hide sdl/libftdi symbols if libraries not found
  MAKEALL: fix check_pipe_status usage
  MAKEALL: remove use of alias in script
  ci: pytest: run test suite on sandbox allyesconfig
  ci: run static analysis on allyesconfig

 .github/workflows/codeql.yml              |  2 +-
 .github/workflows/coverity.sh             |  2 +-
 .github/workflows/test-labgrid-pytest.yml |  4 ++++
 MAKEALL                                   | 14 +++++++-------
 arch/sandbox/Kconfig                      |  6 ++++++
 arch/sandbox/Makefile                     |  4 ++--
 arch/sandbox/os/Makefile                  |  4 ++--
 drivers/gpio/Kconfig                      |  2 +-
 drivers/sound/Kconfig                     |  2 +-
 drivers/video/Kconfig                     |  2 +-
 test/sandbox/allyesconfig.yaml            | 17 +++++++++++++++++
 11 files changed, 43 insertions(+), 16 deletions(-)
 create mode 100644 test/sandbox/allyesconfig.yaml

-- 
2.39.5




             reply	other threads:[~2025-03-26  8:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26  7:59 Ahmad Fatoum [this message]
2025-03-26  7:59 ` [PATCH 1/6] sandbox: use CROSS_PKG_CONFIG when compiling sandbox arch code Ahmad Fatoum
2025-03-26  7:59 ` [PATCH 2/6] sandbox: hide sdl/libftdi symbols if libraries not found Ahmad Fatoum
2025-03-26  7:59 ` [PATCH 3/6] MAKEALL: fix check_pipe_status usage Ahmad Fatoum
2025-03-26  7:59 ` [PATCH 4/6] MAKEALL: remove use of alias in script Ahmad Fatoum
2025-03-26  7:59 ` [PATCH 5/6] ci: pytest: run test suite on sandbox allyesconfig Ahmad Fatoum
2025-03-26  7:59 ` [PATCH 6/6] ci: run static analysis on allyesconfig Ahmad Fatoum
2025-03-27  9:24 ` [PATCH 0/6] ci: run tests and " Sascha Hauer

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=20250326075919.3448789-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=jmaselbas@zdiv.net \
    --cc=jre@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox