From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-27
Date: Wed, 28 Mar 2018 08:00:19 +0200 (CEST) [thread overview]
Message-ID: <20180328060019.4A3AC2084D@mail.bootlin.com> (raw)
Hello,
Build statistics for 2018-03-27
===============================
branch | OK | NOK | TIM | TOT |
2018.02.x | 191 | 10 | 0 | 201 |
Results for branch '2018.02.x'
==============================
Classification of failures by reason
------------------------------------
php-7.2.3 | 4
bluez5_utils-5.48 | 3
cups-filters-1.17.9 | 1
uclibc-ng-test-c6d62cbc6050... | 1
wireshark-2.2.12 | 1
Detail of failures
------------------
xtensa | bluez5_utils-5.48 | NOK | http://autobuild.buildroot.net/results/fd645035990c1bc8190dbaccf81643cd328fba97 |
arm | bluez5_utils-5.48 | NOK | http://autobuild.buildroot.net/results/ac23cfa90887d1bf9baa52fe4931b8ce24fba5ac |
powerpc | bluez5_utils-5.48 | NOK | http://autobuild.buildroot.net/results/a2659afdf2ffe5826ee7dfc49f89fed7c52298e8 |
powerpc64le | cups-filters-1.17.9 | NOK | http://autobuild.buildroot.net/results/74a7f2103b9b7ef7db8f84d9065ae40198565d7e |
x86_64 | php-7.2.3 | NOK | http://autobuild.buildroot.net/results/4f4b72298861c5b3d3cf0d5c1b0b9ad66ab58e95 | ORPH
xtensa | php-7.2.3 | NOK | http://autobuild.buildroot.net/results/e6e6127ce028f93f1de5bae1ea84e778e48227d5 | ORPH
arm | php-7.2.3 | NOK | http://autobuild.buildroot.net/results/33027099916dc7a59bc38acc59bfcfdf0a231658 | ORPH
microblazeel | php-7.2.3 | NOK | http://autobuild.buildroot.net/results/c7e4ec843d15ceaa14683d65071e0f960b3c7e2c | ORPH
i586 | uclibc-ng-test-c6d62cbc6050... | NOK | http://autobuild.buildroot.net/results/4165464b39063508cb271b89fa49a84ed3ebf24a |
i686 | wireshark-2.2.12 | NOK | http://autobuild.buildroot.net/results/d9069fb5cd301482a51bf6ae6e92660ee933791d | ORPH
--
http://autobuild.buildroot.net
reply other threads:[~2018-03-28 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=20180328060019.4A3AC2084D@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