From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] test-pkg: test a subset of toolchains by default, add -a and -n options
Date: Sun, 25 Mar 2018 21:35:52 +0200 [thread overview]
Message-ID: <20180325193552.GO2620@scaer> (raw)
In-Reply-To: <20180325210622.31817922@windsurf>
Thomas, All,
On 2018-03-25 21:06 +0200, Thomas Petazzoni spake thusly:
> On Sun, 25 Mar 2018 10:50:18 +0200, Yann E. MORIN wrote:
> > > Note that the list of toolchains (built in the "toolchains" shell
> > > variable) is no longer sorted. Indeed, when the first N toolchains are
> > > tested, we want them to be tested in the same order as they are listed
> > > in the CSV file, as we are careful to order them in an interesting
> > > order. We only sort when all toolchains are tested.
> >
> > I don't understand why you want to test them in the order they are
> > listed... I understand that you want them to be _selected_ in the order
> > they appear, yes. But tested? See below...
>
> Well, the first 7 toolchains are kind of listed in the order of
> importance, so it makes more sense to *test* the most important
> toolchain first, so if it fails, you can abort there, investigate, and
> then restart the test.
Well, usually I would expect people to fire-and-forget the build, and
check later what is going on. This is not typically something you gaze
at while it is running...
Maybe we should be using that time to plot a Julia like the cool kids? ;-]
> But that's not a strong opinion, so if you disagree with this, I don't
> care that much if the toolchains are tested in alphabetic ordering.
Well, as I said, not a big deal for me either.
I just like that things are consistent, and that, to the user, it looks
nicer to have something that is always sorted, because it is "nice".
With a very personal definition of "nice", that is! ;-]
So, go ahead: if there is no other feedback that requires a respin, just
apply it as-is.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-03-25 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 21:48 [Buildroot] [PATCH v2 0/3] test-pkg: by default only test a subset of toolchains Thomas Petazzoni
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 [this message]
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=20180325193552.GO2620@scaer \
--to=yann.morin.1998@free.fr \
--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