All of lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] [autobuild.buildroot.net] Build results for 2014-09-30
@ 2014-10-01  6:30 Thomas Petazzoni
  2014-10-01 12:51 ` Mike Zick
       [not found] ` <542C5684.8050201@posteo.de>
  0 siblings, 2 replies; 6+ messages in thread
From: Thomas Petazzoni @ 2014-10-01  6:30 UTC (permalink / raw)
  To: buildroot

Build statistics for 2014-09-30
===============================

        success : 121
       failures : 15 
       timeouts : 2  
          TOTAL : 138

Classification of failures by reason
====================================

               alsa-lib-1.0.28 | 2 
                upmpdcli-0.8.1 | 2 
libshairplay-139d5ef5556451... | 1 
                   ushare-1.1a | 1 
           heirloom-mailx-12.5 | 1 
                  nftables-0.3 | 1 
        gst1-plugins-bad-1.4.3 | 1 
                elfutils-0.155 | 1 
             alsa-utils-1.0.28 | 1 
                    ruby-2.1.2 | 1 
    bandwidthd-v2.0.1-auto-r08 | 1 
               valgrind-3.10.0 | 1 
                 tcpdump-4.6.2 | 1 
             subversion-1.7.18 | 1 
                 webkit-1.11.5 | 1 

Detail of failures
===================

         sh4 |                alsa-lib-1.0.28 | NOK | http://autobuild.buildroot.net/results/88ad89f6c4bef430ad43713ef743653a33e054d3/
         sh4 |                alsa-lib-1.0.28 | NOK | http://autobuild.buildroot.net/results/7202edea11ee8e3b241b5d2610f51ff8b6e4ea8e/
         arm |              alsa-utils-1.0.28 | NOK | http://autobuild.buildroot.net/results/2ddb85507ddb0deaa6e9a966a8c0e732ceceeb6f/
      xtensa |     bandwidthd-v2.0.1-auto-r08 | NOK | http://autobuild.buildroot.net/results/8ab7fce71e778b5eeba3b027d6f16f246d1da099/
      mipsel |                 elfutils-0.155 | NOK | http://autobuild.buildroot.net/results/280fdbe2b33e34cc6989364c6df3dd75ecef65ee/
        sh4a |         gst1-plugins-bad-1.4.3 | NOK | http://autobuild.buildroot.net/results/e5d2c4d66387bf6336c5744febee3e32b9f2b1ed/
       nios2 |            heirloom-mailx-12.5 | NOK | http://autobuild.buildroot.net/results/a93fb9ae929c224c02f50c62bea703e60005edbc/
        bfin | libshairplay-139d5ef5556451... | NOK | http://autobuild.buildroot.net/results/f6c6db3e08bf6b95ff22d8665095982f103f53b9/
        bfin |                   nftables-0.3 | NOK | http://autobuild.buildroot.net/results/b053c3162e610545668e79e35683a22563d65071/
        bfin |                     ruby-2.1.2 | NOK | http://autobuild.buildroot.net/results/f981e6f3aef0252ac686cfd2951547008a263819/
    mips64el |              subversion-1.7.18 | TIM | http://autobuild.buildroot.net/results/0a4a88a695ad411c79ab195dd5bfbcf917ee503b/
      x86_64 |                  tcpdump-4.6.2 | TIM | http://autobuild.buildroot.net/results/c05ac21feb10318c8e31baffd47deb94aac0fc4a/
         sh4 |                 upmpdcli-0.8.1 | NOK | http://autobuild.buildroot.net/results/e5be8fe46a30f0b417fe5fc19a27c480d885791e/
         sh4 |                 upmpdcli-0.8.1 | NOK | http://autobuild.buildroot.net/results/a3453afddff4fc03681f7fbdff3ccab9706eb189/
        bfin |                    ushare-1.1a | NOK | http://autobuild.buildroot.net/results/d91009e827b828857253d3681d66024d3f1cf623/
     powerpc |                valgrind-3.10.0 | NOK | http://autobuild.buildroot.net/results/2d2c2c2076312a6c77f39eaeffd1ad17f9b23d4e/
         arm |                  webkit-1.11.5 | NOK | http://autobuild.buildroot.net/results/6e7086abbc4b7b5b9e022d656b02e854f6d80a7a/


-- 
http://autobuild.buildroot.net

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Build results for 2014-09-30
  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
       [not found] ` <542C5684.8050201@posteo.de>
  1 sibling, 1 reply; 6+ messages in thread
From: Mike Zick @ 2014-10-01 12:51 UTC (permalink / raw)
  To: buildroot

Some noise from one of your read-mostly M.L. members again (me).

> On Wed,  1 Oct 2014 08:30:12 +0200 (CEST)
> Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
>
> Build statistics for 2014-09-30
> ===============================
> 
>         success : 121
>        failures : 15 
>        timeouts : 2  
>           TOTAL : 138
> 

Looking good for so early in the cycle.

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" ?

Mike

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Build results for 2014-09-30
  2014-10-01 12:51 ` Mike Zick
@ 2014-10-01 16:23   ` Thomas Petazzoni
  2014-10-01 16:38     ` Mike Zick
  2014-10-02  8:54     ` Luca Ceresoli
  0 siblings, 2 replies; 6+ messages in thread
From: Thomas Petazzoni @ 2014-10-01 16:23 UTC (permalink / raw)
  To: buildroot

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Build results for 2014-09-30
  2014-10-01 16:23   ` Thomas Petazzoni
@ 2014-10-01 16:38     ` Mike Zick
  2014-10-02  8:54     ` Luca Ceresoli
  1 sibling, 0 replies; 6+ messages in thread
From: Mike Zick @ 2014-10-01 16:38 UTC (permalink / raw)
  To: buildroot

On Wed, 1 Oct 2014 18:23:22 +0200
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> 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.
>

Good point.

Perhaps just as a one-line __suggestion__ somewhere?

Mike

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Build results for 2014-09-30
       [not found]   ` <20141001213513.1dedb82c@free-electrons.com>
@ 2014-10-01 19:41     ` Jörg Krause
  0 siblings, 0 replies; 6+ messages in thread
From: Jörg Krause @ 2014-10-01 19:41 UTC (permalink / raw)
  To: buildroot


On 10/01/2014 09:35 PM, Thomas Petazzoni wrote:
> Dear J?rg Krause,
>
> On Wed, 01 Oct 2014 21:31:16 +0200, J?rg Krause wrote:
>> On 10/01/2014 08:30 AM, Thomas Petazzoni wrote:
>>> Build statistics for 2014-09-30
>>> ===============================
>>>
>>>            sh4 |                 upmpdcli-0.8.1 | NOK | http://autobuild.buildroot.net/results/e5be8fe46a30f0b417fe5fc19a27c480d885791e/
>> missing <cstdio>.
>>
>>>            sh4 |                 upmpdcli-0.8.1 | NOK | http://autobuild.buildroot.net/results/a3453afddff4fc03681f7fbdff3ccab9706eb189/
>> same.
>>
>> I will inform the developer of upmpdcli and submit a patch soon.
> Great, thanks a lot!
>

Hi Thomas,

I have a question to the patch you added to upmpdcli some month ago. You 
added among other things #define _GNU_SOURCE to upmpd/upmpdutils.cxx. 
Can you remember why?

The developer of upmpdcli asked me...he wants to submit the patch upstream.

Best regards
J?rg Krause

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Build results for 2014-09-30
  2014-10-01 16:23   ` Thomas Petazzoni
  2014-10-01 16:38     ` Mike Zick
@ 2014-10-02  8:54     ` Luca Ceresoli
  1 sibling, 0 replies; 6+ messages in thread
From: Luca Ceresoli @ 2014-10-02  8:54 UTC (permalink / raw)
  To: buildroot

Dear Thomas,

Thomas Petazzoni wrote:
> Hello,
>
> On Wed, 1 Oct 2014 07:51:16 -0500, Mike Zick wrote:
...
>> 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.

I appreciate when people do that. It makes the commit more
self-explanatory, and it's very handy to search with git log, among
other things.

But I agree it should not be mandatory.

-- 
Luca

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2014-10-02  8:54 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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

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.