From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-05-16
Date: Sat, 18 May 2013 13:38:44 +0200 [thread overview]
Message-ID: <20130518113844.GA3050@free.fr> (raw)
In-Reply-To: <20130517200122.42592574@skate>
On 2013-05-17 20:01 +0200, Thomas Petazzoni spake thusly:
> On Fri, 17 May 2013 08:30:04 +0200 (CEST), Thomas Petazzoni wrote:
> > Build statistics for 2013-05-16
> > ===============================
> >
> > success : 79
> > failures : 47
> > timeouts : 3
> > TOTAL : 129
>
> I have augmented the timeout duration from 2 hours to 4 hours, which
> should hopefully help get rid of those false positives.
Sounds good.
> Also, I propose to remove the timeouts from the list of failures in the
> automated e-mail, and only list them in the success/failures/timeouts
> summary above. They're just noise in the list of failures. Any
> objection to this?
If the timeouts number rises again, we can then start investigating.
Until then, they are just spurious, and I doubt they are really
meaningfull. So, I agree, let's remove them from the report.
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. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2013-05-18 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-05-16 Thomas Petazzoni
2013-05-17 18:01 ` Thomas Petazzoni
2013-05-18 11:38 ` Yann E. MORIN [this message]
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=20130518113844.GA3050@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox