From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/6] support/test-pkg: report number and types of failures
Date: Sat, 11 Feb 2017 23:21:51 +0100 [thread overview]
Message-ID: <20170211222151.GD20146@free.fr> (raw)
In-Reply-To: <CAAXf6LW6WkZx=KZTTVt9vSuq7kChPfa2sXMhYAPYh2MN53cwgw@mail.gmail.com>
Thomas DS, All,
On 2017-02-11 20:48 +0100, Thomas De Schampheleire spake thusly:
> On Thu, Feb 9, 2017 at 10:59 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > Hello,
> >
> > On Wed, 8 Feb 2017 21:15:26 +0100, Yann E. MORIN wrote:
> >
> >> + if [ ${nb_dl} -ne 0 ]; then
> >> + printf "%d configurations could not be downloaded\n" ${nb_dl}
> >> + fi
> >> + if [ ${nb_cfg} -ne 0 ]; then
> >> + printf "%d configurations could not be applied\n" ${nb_cfg}
> >> + fi
> >> + if [ ${nb_skip} -ne 0 ]; then
> >> + printf "%d configurations were skipped\n" ${nb_skip}
> >> + fi
> >> + if [ ${nb_clean} -ne 0 ]; then
> >> + printf "%d configurations could not be dircleaned\n" ${nb_clean}
> >> + fi
> >> + if [ ${nb_build} -ne 0 ]; then
> >> + printf "%d configurations would not build\n" ${nb_build}
> >> + fi
> >
> > This is really verbose and not very useful. Instead what would be much
> > more useful is just:
> >
> > successes = %d, failures = %d, skipped = %d
> >
> > (possibly presented in a different way, my point is really that number
> > of successes, number of failures and numbers of skipped configurations
> > is really all what matters)
> >
>
> I agree with Thomas here. Especially because a failure in download,
> olddefconfig and dirclean steps is exceptional. Most failures will be
> due to build problems or to a lesser extent invalid cofigurations
> (either completely invalid == developer error in providing the
> snippet, or invalid in some toolchains only).
> Since the amount of toolchains that will be checked is limited, it is
> not a lot of work to scroll up to view the actual problems.
I already fixed it as per Thomas P. suggestion. It will be in the next
re-spin (tomorrow).
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:[~2017-02-11 22:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 20:15 [Buildroot] [PATCH 0/6 v3] support: script to build-test packages Yann E. MORIN
2017-02-08 20:15 ` [Buildroot] [PATCH 1/6] support/scripts: add script to test a package Yann E. MORIN
2017-02-08 22:00 ` Cam Hutchison
2017-02-08 22:39 ` Cam Hutchison
2017-02-11 16:08 ` Yann E. MORIN
2017-02-11 21:19 ` Thomas De Schampheleire
2017-02-11 22:28 ` Yann E. MORIN
2017-02-09 13:41 ` Luca Ceresoli
2017-02-09 21:50 ` Thomas Petazzoni
2017-02-09 22:00 ` Yann E. MORIN
2017-02-09 21:51 ` Thomas Petazzoni
2017-02-08 20:15 ` [Buildroot] [PATCH 2/6] support/test-pkg: store lines missing from resulting configuraiton Yann E. MORIN
2017-02-09 17:07 ` Luca Ceresoli
2017-02-09 21:58 ` Thomas Petazzoni
2017-02-08 20:15 ` [Buildroot] [PATCH 3/6] support/test-pkg: report number and types of failures Yann E. MORIN
2017-02-09 17:09 ` Luca Ceresoli
2017-02-09 21:59 ` Thomas Petazzoni
2017-02-11 19:48 ` Thomas De Schampheleire
2017-02-11 22:21 ` Yann E. MORIN [this message]
2017-02-08 20:15 ` [Buildroot] [PATCH 4/6] supprt/test-pkg: add option to limit the number of tests Yann E. MORIN
2017-02-09 22:13 ` Thomas Petazzoni
2017-02-08 20:15 ` [Buildroot] [PATCH 5/6] support/test-pkg: add option to use an alternate list of toolchains Yann E. MORIN
2017-02-11 19:53 ` Thomas De Schampheleire
2017-02-11 22:24 ` Yann E. MORIN
2017-02-08 20:15 ` [Buildroot] [PATCH 6/6] support/test-pkg: print number of toolchain and progress Yann E. MORIN
2017-02-11 20:09 ` Thomas De Schampheleire
2017-02-11 22:25 ` Yann E. MORIN
2017-02-12 6:40 ` Thomas De Schampheleire
2017-02-12 9:33 ` 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=20170211222151.GD20146@free.fr \
--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 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.