From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 0/5] gitlab Qemu runtime testing
Date: Sun, 12 Apr 2020 16:11:55 +0200 [thread overview]
Message-ID: <20200412161155.51b6bc98@windsurf.home> (raw)
In-Reply-To: <20200217205030.8157-1-romain.naour@smile.fr>
Hello,
On Mon, 17 Feb 2020 21:50:25 +0100
Romain Naour <romain.naour@smile.fr> wrote:
> Jugurtha BELKALEM (2):
> support/scripts/boot-qemu-image.py: boot Qemu images with Qemu-system.
> gitlab.yml.in*: enable Qemu gitlab testing
>
> Romain Naour (3):
> board/qemu: add defconfig file name as tag after the qemu command line
> board/qemu: add post-image script for gitlab qemu testing
> configs/qemu*: use the post-image script with "$(BR2_DEFCONFIG)" as
> argument.
Overall, I am quite happy with the series. There are just two things
that I am not entirely sure about:
(1) The logic that tests $CI_JOB_NAME in board/qemu/post-image.sh, to
test if we are running under Gitlab CI or not. It feels a bit
hackish to me. Should this magic be there, or instead tweaked by
the Gitlab CI testing stuff directly ?
(2) We now generate this start-qemu.sh script in $(BINARIES_DIR), but
in fact only really use it for Gitlab CI testing. Should we make
this start-qemu.sh script more prominently useful ? Or should we
instead not have any start-qemu.sh script, and have the Gitlab CI
testing logic directly find what the Qemu command line should be ?
That being said, this series has been around for a long time, so unless
I get some feedback on these questions, I'm going to apply it as-is, we
can always improve on top of that later on.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-04-12 14:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 20:50 [Buildroot] [PATCH v5 0/5] gitlab Qemu runtime testing Romain Naour
2020-02-17 20:50 ` [Buildroot] [PATCH v5 1/5] board/qemu: add defconfig file name as tag after the qemu command line Romain Naour
2020-02-17 20:50 ` [Buildroot] [PATCH v5 2/5] board/qemu: add post-image script for gitlab qemu testing Romain Naour
2020-04-13 7:25 ` Yann E. MORIN
2020-02-17 20:50 ` [Buildroot] [PATCH v5 3/5] configs/qemu*: use the post-image script with "$(BR2_DEFCONFIG)" as argument Romain Naour
2020-02-17 20:50 ` [Buildroot] [PATCH v5 4/5] support/scripts/boot-qemu-image.py: boot Qemu images with Qemu-system Romain Naour
2020-04-13 7:15 ` Yann E. MORIN
2020-04-13 21:38 ` Romain Naour
2020-02-17 20:50 ` [Buildroot] [PATCH v5 5/5] gitlab.yml.in*: enable Qemu gitlab testing Romain Naour
2020-04-12 14:11 ` Thomas Petazzoni [this message]
2020-04-12 20:00 ` [Buildroot] [PATCH v5 0/5] gitlab Qemu runtime testing Romain Naour
2020-04-13 19:56 ` Yann E. MORIN
2020-04-13 20:03 ` Romain Naour
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=20200412161155.51b6bc98@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.