Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-09-30
Date: Wed, 1 Oct 2014 18:23:22 +0200	[thread overview]
Message-ID: <20141001182322.53f6fd68@free-electrons.com> (raw)
In-Reply-To: <20141001075116.7913ff52@core2quad.morethan.org>

Hello,

On Wed, 1 Oct 2014 07:51:16 -0500, Mike Zick wrote:

> > Build statistics for 2014-09-30
> > ===============================
> > 
> >         success : 121
> >        failures : 15 
> >        timeouts : 2  
> >           TOTAL : 138
> > 
> 
> Looking good for so early in the cycle.

Yes, even though 138 is a bit limited in terms of build numbers for one
day. I believe there were some issues with the Buildroot Git server
lately, maybe this has slowed down the autobuilders a bit. We used to
have in the order of 200-220 builds per day. Hum, looking more, seems
like all the autobuilders from Peter are no longer submitting build
results.

Peter?

> Now the noise:
> 
> I have noticed that recently some of the fix contributors
> have been including a "few line" quote of a typical error
> message in addition to the "fix(es): url" comment.
> 
> As a read-mostly member, I find that new (habit? practice?)
> very helpful when reading the daily M.L. fix messages.
> 
> Q:
> Should there be a discussion on making this additional
> information a BR "recommended practice" ?

I personally don't have a strong opinion. Since the autobuilder URLs
are stable, and supposed to be kept around forever, I don't mind seeing
only the autobuilder URL. But if the submitter decides to include a
portion of the error message, then fine as well. We could imagine that
doing this would give a better change of people googling for the error
message, to stumble across the relevant Buildroot patch rather than
just the autobuilder results.

Not sure I want to make this a mandatory thing, though. We already have
a lot of requirements, and doing autobuilder fixes is already not that
fun, so if we raise the barrier too much, this might discourage
contributors.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-10-01 16:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-09-30 Thomas Petazzoni
2014-10-01 12:51 ` Mike Zick
2014-10-01 16:23   ` Thomas Petazzoni [this message]
2014-10-01 16:38     ` Mike Zick
2014-10-02  8:54     ` Luca Ceresoli
     [not found] ` <542C5684.8050201@posteo.de>
     [not found]   ` <20141001213513.1dedb82c@free-electrons.com>
2014-10-01 19:41     ` Jörg Krause

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=20141001182322.53f6fd68@free-electrons.com \
    --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