All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-06-20
Date: Wed, 21 Jun 2017 15:50:07 +0200	[thread overview]
Message-ID: <CAMRc=Me_-5xaUkmsbj36VQwyohns+iRTc5Wny+bCDPmGSi_FCg@mail.gmail.com> (raw)
In-Reply-To: <20170621063055.D2EE6208DF@mail.free-electrons.com>

2017-06-21 8:30 GMT+02:00 Thomas Petazzoni
<thomas.petazzoni@free-electrons.com>:
> Hello,
>
> Build statistics for 2017-06-20
> ================================
>
>       successes : 118
>        failures : 935
>        timeouts : 0
>           TOTAL : 1053
>
> Classification of failures by reason
> ====================================
>
>               host-expat-2.2.1 | 449
>                    expat-2.2.1 | 422
>      python-cryptography-1.7.2 | 11
>               alsa-lib-1.1.4.1 | 6
>                 kvazaar-v1.1.0 | 6
> knock-258a27e5a47809f97c2b9... | 5
>            argp-standalone-1.3 | 4
>                 busybox-1.26.2 | 4
>        linuxconsoletools-1.6.0 | 4
>                    attr-2.4.47 | 3
> dropwatch-7c33d8a8ed105b07a... | 2
>                      gpsd-3.16 | 2
>                 beecrypt-4.2.1 | 1
>                 bellagio-0.9.3 | 1
>                   cc-tool-0.26 | 1
>                   check-0.11.0 | 1
>                   cppcms-1.0.5 | 1
>                      efivar-30 | 1
>                gnuradio-3.7.11 | 1
>            host-doxygen-1.8.13 | 1

FYI I've submitted a pull request[1] fixing the host-doxygen build
failures that have been popping up recently. Let's wait and see if it
can be merged upstream and then include it in buildroot too.

Best regards,
Bartosz Golaszewski

[1] https://github.com/doxygen/doxygen/pull/574

  reply	other threads:[~2017-06-21 13:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2017-06-20 Thomas Petazzoni
2017-06-21 13:50 ` Bartosz Golaszewski [this message]
2017-06-21 16:57 ` Koen Martens

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='CAMRc=Me_-5xaUkmsbj36VQwyohns+iRTc5Wny+bCDPmGSi_FCg@mail.gmail.com' \
    --to=brgl@bgdev.pl \
    --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 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.