From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/3] test-pkg: by default only test a subset of toolchains
Date: Fri, 23 Mar 2018 22:48:12 +0100 [thread overview]
Message-ID: <20180323214815.19831-1-thomas.petazzoni@bootlin.com> (raw)
During the Buildroot Developers meeting at ELCE 2017, we discussed how
to make test-pkg more usable for our contributors. Our idea is that
test-pkg should not test all toolchains by default, but only a smaller
subset of "interesting" toolchains, that exhibit the most common
problems we encounter with new packages.
This series does that by:
- Adjust the toolchain CSV file to have the interesting toolchains
first, adding comments and empty lines along the way to clarify
what is going on.
- Update test-pkg to test only the first 7 toolchains, add a --all
option to test all toolchains, and a --number option to test only
the first N toolchains.
- Update the Buildroot manual accordingly.
Thanks!
Thomas
Changes since v1:
- Drop the first two patches, since they have been merged.
- In the CSV list of toolchains, add better comments to explain the
two "sections" of the toolchain list, as suggested by Yann
E. Morin.
- In the test-pkg script changes themselves:
- Keep alphabetic sorting in the definition of the 'o' variable that
contains the list of short options. Suggested by Yann E. Morin. 'h'
for help remains a special case and therefore remains at the first
position.
- Keep alphabetic sorting when handling options. Here as well, --help
remains first, as it already was. Suggested by Yann E. Morin.
- Use spaces and not tabs for indentation. Suggested by Yann E. Morin.
Thomas Petazzoni (3):
toolchain-configs.csv: re-organize for test-pkg
test-pkg: test a subset of toolchains by default, add -a and -n
options
docs/manual: update the documentation about test-pkg
docs/manual/adding-packages-tips.txt | 11 +++--
.../autobuild/toolchain-configs.csv | 32 ++++++++++---
utils/test-pkg | 56 +++++++++++++++++++---
3 files changed, 83 insertions(+), 16 deletions(-)
--
2.14.3
next reply other threads:[~2018-03-23 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 21:48 Thomas Petazzoni [this message]
2018-03-23 21:48 ` [Buildroot] [PATCH v2 1/3] toolchain-configs.csv: re-organize for test-pkg Thomas Petazzoni
2018-03-24 15:48 ` Yann E. MORIN
2018-04-01 14:31 ` Thomas Petazzoni
2018-03-23 21:48 ` [Buildroot] [PATCH v2 2/3] test-pkg: test a subset of toolchains by default, add -a and -n options Thomas Petazzoni
2018-03-24 2:39 ` Matthew Weber
2018-03-25 8:50 ` Yann E. MORIN
2018-03-25 19:06 ` Thomas Petazzoni
2018-03-25 19:35 ` Yann E. MORIN
2018-03-23 21:48 ` [Buildroot] [PATCH v2 3/3] docs/manual: update the documentation about test-pkg Thomas Petazzoni
2018-03-25 8:12 ` Yann E. MORIN
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=20180323214815.19831-1-thomas.petazzoni@bootlin.com \
--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