From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-11-08
Date: Thu, 9 Nov 2017 12:42:49 +0100 [thread overview]
Message-ID: <20171109124249.4f57a264@windsurf> (raw)
In-Reply-To: <20171109072720.ysow3pwt4igf5vva@tarshish>
Hello,
On Thu, 9 Nov 2017 09:27:20 +0200, Baruch Siach wrote:
> > Build statistics for 2017-11-08
> > ===============================
> >
> > branch | OK | NOK | TIM | TOT |
> > master | 142 | 31 | 0 | 173 |
> > 2017.08.x | 6 | 0 | 0 | 6 |
>
> Nice. Thanks for working on that.
You're welcome :)
However, in fact, it was not really planned to be deployed today, I
forgot yesterday evening to revert the script to its original state.
The support is not complete yet, and due to my changes, the individual
e-mails normally sent to each developer have not been sent today.
> > Results for branch 'master'
> > ===========================
The name of the branch is here ^^^
> > Detail of failures
> > ------------------
>
> Having an additional 'branch' column here might be useful now.
The list of failures below is only for the master branch, as you're in
the "Results for branch 'master'".
Failures for other branches would show up in another section "Results
for branch '2017.08.x'". However, since there has been 0 failures on
2017.08.x yesterday, the section was not generated at all (which is
expected).
Let me know if that is unclear and if you have a better proposal.
Mixing the results in the same table was to me not a good option, as we
clearly don't want the "List of failures by reason" to contain results
for multiple branches, as this classification only makes sense per
branch. That's why I opted for one section per branch, rather than
mixing the results together. I'm open to other suggestions, as the
drawback of my solution is the length of the e-mail.
> Unrelated to that (I think), DNS resolution for autobuild.buildroot.net looks
> strange this morning:
>
> $ host autobuild.buildroot.net
> autobuild.buildroot.net is an alias for ks383786.kimsufi.com.
> ks383786.kimsufi.com has address 94.23.254.152
Peter explained that it is normal. The server is now back up :)
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-09 11:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2017-11-08 Thomas Petazzoni
2017-11-09 7:27 ` Baruch Siach
2017-11-09 8:30 ` Yann E. MORIN
2017-11-09 10:34 ` Peter Korsgaard
2017-11-09 10:57 ` Baruch Siach
2017-11-09 11:42 ` Thomas Petazzoni [this message]
2017-11-09 15:55 ` Baruch Siach
2017-11-09 15:57 ` Thomas Petazzoni
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=20171109124249.4f57a264@windsurf \
--to=thomas.petazzoni@free-electrons.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