Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-07-19
Date: Mon, 20 Jul 2015 15:44:08 +0300	[thread overview]
Message-ID: <20150720124408.GM13027@tarshish> (raw)
In-Reply-To: <CA+BsyQ4=X7ZA0LTiHNo4SAC2FotUJGL+3xb1LgjNjFUQCUBk+g@mail.gmail.com>

Hi Brendan,

On Mon, Jul 20, 2015 at 01:30:24PM +0100, Brendan Heading wrote:
> On 20 July 2015 at 07:30, Thomas Petazzoni <
> thomas.petazzoni at free-electrons.com> wrote:
> 
> > Build statistics for 2015-07-19
> > ===============================
> >
> >         success : 230
> >        failures : 125
> >        timeouts : 6
> >           TOTAL : 361
> >
> > Classification of failures by reason
> > ====================================
> >
> 
> [..]
> 
> hi all, new to the buildroot list - I have some free time, and I've been
> using buildroot for a while in projects with my previous employer, so I'm
> keen to repay some of the time and effort it has saved me in the past. This
> list of bugs looks like a great place to start ;)
> 
> Shall I just begin to submit patches or are there likely to be people
> already looking at these issues ?

Welcome. Looking into autobuild issues and posting patches is a great way to 
start. Make sure to read 
http://nightly.buildroot.org/manual.html#_analyzing_and_fixing_autobuild_failures
before you start. An overlap in autobuild issues fixing happen at times, but 
it's quite rare. Anyone is allowed and encouraged to post build failure fixes, 
as well as run-time failures, though the autobuilder currently doesn't catch 
failures of the latter type.

> The fan-ctrl failure for all arches looks like it might have been a
> sourceforge problem. The package is fetched from a sourceforge svn
> repository (regular package tarball downloads from sourceforge look OK).
> Maybe sourceforge have been fiddling with things, I haven't checked.

It most likely has to do with recent sourceforge infrastructure issues 
(http://sourceforge.net/blog/sourceforge-infrastructure-and-service-restoration/).

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  parent reply	other threads:[~2015-07-20 12:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-07-19 Thomas Petazzoni
2015-07-20 12:30 ` Brendan Heading
2015-07-20 12:39   ` Thomas Petazzoni
2015-07-20 12:44   ` Baruch Siach [this message]
2015-07-20 12:49     ` Brendan Heading
2015-07-20 13:10       ` Thomas Petazzoni
2015-07-20 13:54         ` Brendan Heading
2015-07-20 19:55 ` Jörg Krause
2015-07-20 20:38   ` Thomas Petazzoni
2015-07-20 20:48     ` 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=20150720124408.GM13027@tarshish \
    --to=baruch@tkos.co.il \
    --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