From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 0/1] GitHub actions for barebox
Date: Thu, 4 May 2023 10:58:26 +0200 [thread overview]
Message-ID: <20230504085827.484198-1-s.hauer@pengutronix.de> (raw)
This adds support for GitHub actions to compile barebox and to do some
basic runtime tests on emulated machines.
A container is set up with Crosstool toolchains installed for most
architectures in barebox (kvx is missing currently). This is used to
compile all defconfigs. See
https://github.com/barebox/barebox/actions/runs/4880635125 for the
results of the current next branch.
The runtime tests can be seen here:
https://github.com/barebox/barebox/actions/runs/4880635129 . barebox
starts on several emulated ARM/Mips/riscv/x86 machines. This shows that
the boards come up. Additionally the barebox selftests are enabled and
run on the boards.
This is all far from being perfect, but it's a start. I'd be glad to get
some comments and/or suggestions how this could be improved, I am still
a beginner when it comes to GitHub actions. Also suggestions what else
could be tested would be welcomed on our way to get better releases in
the future.
For those of you who are not familiar with GitHub actions: You can
easily run the tests yourself. Just fork the barebox repository on
GitHub and push some branch based on the current next branch to it.
Head over to the "Actions" tab and wait/look for the results.
Sascha
Sascha Hauer (1):
Add GitHub CI
.github/workflows/container.yml | 32 ++++++++
.github/workflows/test-defconfigs.yml | 44 +++++++++++
.github/workflows/test-labgrid-pytest.yml | 70 ++++++++++++++++++
test/Containerfile | 89 +++++++++++++++++++++++
test/generate-dummy-fw.sh | 62 ++++++++++++++++
test/kconfig/disable_size_check.kconf | 1 +
test/kconfig/disable_target_tools.kconf | 5 ++
test/kconfig/enable_self_test.kconf | 5 ++
8 files changed, 308 insertions(+)
create mode 100644 .github/workflows/container.yml
create mode 100644 .github/workflows/test-defconfigs.yml
create mode 100644 .github/workflows/test-labgrid-pytest.yml
create mode 100644 test/Containerfile
create mode 100755 test/generate-dummy-fw.sh
create mode 100644 test/kconfig/disable_size_check.kconf
create mode 100644 test/kconfig/disable_target_tools.kconf
create mode 100644 test/kconfig/enable_self_test.kconf
--
2.39.2
next reply other threads:[~2023-05-04 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 8:58 Sascha Hauer [this message]
2023-05-04 8:58 ` [PATCH 1/1] Add GitHub CI 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=20230504085827.484198-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox