From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-30
Date: Sat, 31 Mar 2018 08:00:12 +0200 (CEST) [thread overview]
Message-ID: <20180331060012.892B920723@mail.bootlin.com> (raw)
Hello,
Build statistics for 2018-03-30
===============================
branch | OK | NOK | TIM | TOT |
2018.02.x | 168 | 9 | 0 | 177 |
master | 6 | 0 | 0 | 6 |
Results for branch '2018.02.x'
==============================
Classification of failures by reason
------------------------------------
bluez5_utils-5.48 | 3
jamvm-2.0.0 | 2
php-7.2.3 | 1
qt5webkit-5.9.1 | 1
systemd-237 | 1
uclibc-ng-test-c6d62cbc6050... | 1
Detail of failures
------------------
xtensa | bluez5_utils-5.48 | NOK | http://autobuild.buildroot.net/results/482947487b2989aabe59b61e7fe1cde1b4d5fed1 |
arm | bluez5_utils-5.48 | NOK | http://autobuild.buildroot.net/results/d879bff6431bb0595705d42c20319812119b423b |
arm | bluez5_utils-5.48 | NOK | http://autobuild.buildroot.net/results/a5c202d0fa46ab44f01a398a4dd101d9eff4e9b1 |
mipsel | jamvm-2.0.0 | NOK | http://autobuild.buildroot.net/results/f23a66f658860a81fb7bb1ecfd32c87af075e0e7 | ORPH
mipsel | jamvm-2.0.0 | NOK | http://autobuild.buildroot.net/results/ce0aceebefd80dbe37ed344c2fd19626833ef5c5 | ORPH
mips64el | php-7.2.3 | NOK | http://autobuild.buildroot.net/results/43dd4dbdb32d3074c93f277ef9e2bdad239952f8 | ORPH
mipsel | qt5webkit-5.9.1 | NOK | http://autobuild.buildroot.net/results/83f1889dcf9dc5c07b3d44ad3e2f31ebc0c4b1fe |
powerpc | systemd-237 | NOK | http://autobuild.buildroot.net/results/47d163759fafac990f2f3af5b5fbf261a8cf89e5 |
i586 | uclibc-ng-test-c6d62cbc6050... | NOK | http://autobuild.buildroot.net/results/19b6d20c1e2985d637791b6c6499823d9d982b1f |
--
http://autobuild.buildroot.net
reply other threads:[~2018-03-31 6:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180331060012.892B920723@mail.bootlin.com \
--to=thomas.petazzoni@bootlin.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