From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-07-31
Date: Fri, 4 Aug 2017 22:01:13 +0200 [thread overview]
Message-ID: <5fddab52-cf68-20a3-2c57-efea72323008@gmail.com> (raw)
In-Reply-To: <20170801063048.E1A5E20C14@mail.free-electrons.com>
Hi Thomas,
Le 01/08/2017 ? 08:30, Thomas Petazzoni a ?crit :
> Hello,
>
> Build statistics for 2017-07-31
> ================================
>
> successes : 165
> failures : 18
> timeouts : 0
> TOTAL : 183
>
> Classification of failures by reason
> ====================================
>
> gpsd-3.16 | 2
> libspatialindex-1.8.5 | 1
>
> Detail of failures
> ===================
>
> microblazeel | gpsd-3.16 | NOK | http://autobuild.buildroot.net/results/64a0bec7efe5b63a2b315bd204fb50884d62f0a8 |
> microblazeel | gpsd-3.16 | NOK | http://autobuild.buildroot.net/results/4c240106fb29805382d5ae347e65b6f83d5033d4 |
> microblazeel | libspatialindex-1.8.5 | NOK | http://autobuild.buildroot.net/results/3cd4bb438158e6f848072af1acae876a8a44ef88 |
Following the removal of gdb on microblaze, what do we do for this toolchain
issue? You reported the bug last year without any feedback [1].
I would suggest adding an autobuilder exception on these two packages.
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69401
Best regards,
Romain
next prev parent reply other threads:[~2017-08-04 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2017-07-31 Thomas Petazzoni
2017-08-04 20:01 ` Romain Naour [this message]
2017-08-04 20:13 ` Arnout Vandecappelle
2017-08-04 20:23 ` Romain Naour
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=5fddab52-cf68-20a3-2c57-efea72323008@gmail.com \
--to=romain.naour@gmail.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 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.