From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] new builtin kernel with entropy for the test infra
Date: Sat, 3 Aug 2019 08:24:34 +0200 [thread overview]
Message-ID: <20190803082434.0080779f@windsurf.home> (raw)
In-Reply-To: <20190803052216.22292-1-ricardo.martincoski@gmail.com>
Hello,
On Sat, 3 Aug 2019 02:22:12 -0300
Ricardo Martincoski <ricardo.martincoski@gmail.com> wrote:
> This small series adds a new builtin kernel image to the test infra.
> It contains the VirtIORNG driver so the target will have enough entropy at
> startup, a requirement for more and more packages being tested.
>
> It also uses this new builtin kernel to speed-up some test cases (atop,
> syslog-ng, python-crossbar, python-nacl) and fix others (python-txtorcon,
> python-treq).
>
> The binaries I used can be found here [1] and have this version string:
> >Linux version 4.19.16 (br-user at runner-ed2dce3a-project-3755559-concurrent-0) (gcc version 4.9.4 (Buildroot 2017.08-git-01078-g95b1dae)) #1 Fri Aug 2 23:05:09 UTC 2019
>
> One can see a complete run of "-runtime-tests" before [2] and after [3] this
> series in the URLs below.
>
> In order to provide a v1 of this series, I created a naming convention for the
> artifacts and also for the string passed to emulator.py in parameter "kernel".
> It was the first naming that came to mind, so of course it is open to
> suggestions/improvements.
>
> [1] https://gitlab.com/RicardoMartincoski/buildroot/commit/2ed44c7471cf5db246b592e24e9b2cfd69702f0f
> [2] https://gitlab.com/RicardoMartincoski/buildroot/pipelines/74501223
> [3] https://gitlab.com/RicardoMartincoski/buildroot/pipelines/74516103
Thanks a lot for working on this. However, instead of having this new
kernel as a separate "version" from the current ARMv5 pre-built kernel,
why don't we simply update the existing one ?
One issue is that downloads get cached, so if the filename is the same,
it won't be redownloaded. Perhaps we need to store hashes of the
download artifacts, so that we can detect if they need to be
re-downloaded ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-03 6:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 5:22 [Buildroot] [PATCH 0/4] new builtin kernel with entropy for the test infra Ricardo Martincoski
2019-08-03 5:22 ` [Buildroot] [PATCH 1/4] support/testing: add builtin armv5 kernel 4.19 with entropy Ricardo Martincoski
2019-08-03 12:51 ` Peter Korsgaard
2019-10-16 9:50 ` Arnout Vandecappelle
2019-10-16 10:05 ` Arnout Vandecappelle
2019-08-03 5:22 ` [Buildroot] [PATCH 2/4] support/testing: test syslog-ng with builtin kernel Ricardo Martincoski
2019-08-03 12:52 ` Peter Korsgaard
2019-08-03 5:22 ` [Buildroot] [PATCH 3/4] support/testing: test python-* " Ricardo Martincoski
2019-08-03 12:52 ` Peter Korsgaard
2019-08-03 5:22 ` [Buildroot] [PATCH 4/4] support/testing: test atop " Ricardo Martincoski
2019-08-03 12:52 ` Peter Korsgaard
2019-08-03 6:24 ` Thomas Petazzoni [this message]
2019-08-03 11:24 ` [Buildroot] [PATCH 0/4] new builtin kernel with entropy for the test infra Arnout Vandecappelle
2019-08-03 12:26 ` Peter Korsgaard
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=20190803082434.0080779f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox