From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-01-03
Date: Thu, 4 Jan 2018 15:42:36 +0100 [thread overview]
Message-ID: <12466b9b-4377-b65c-bdb7-c76b136fc3ef@gmail.com> (raw)
In-Reply-To: <20180104070035.EEAA2207B1@mail.free-electrons.com>
Hi Matt,
Le 04/01/2018 ? 08:00, Thomas Petazzoni a ?crit?:
> Hello,
>
> Build statistics for 2018-01-03
> ===============================
>
> x86_64 | unknown | TIM | http://autobuild.buildroot.net/results/254910c41ec0fbf36db86b377d3f237e4d176515 |
> aarch64 | unknown | TIM | http://autobuild.buildroot.net/results/8f153e997b5c371817388f02dbe6c7fea8857f52 |
I'm using your patch "hung build: convert to monitor thread" v2 and it seems
there is a corner case with boost package and the sanitize rpath script.
I don't understand why the timeout is trigged here.
I've rebuilt boost on the autobuilder without any issue.
Do you have an idea ?
Here is the log for the instance-0 (boost):
[Wed, 03 Jan 2018 16:33:07] INFO: generate the configuration
KCONFIG_SEED=0x9710AB02
[Wed, 03 Jan 2018 16:34:04] INFO: build started
[Wed, 03 Jan 2018 21:20:34] INFO: build hung
[Wed, 03 Jan 2018 21:20:40] INFO: build timed out [-9]
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0
100 29030 0 0 100 29030 0 9676 0:00:03 0:00:03 --:--:-- 7818
100 29274 0 244 100 29030 81 9676 0:00:03 0:00:03 --:--:-- 7823
Best regards,
Romain
next prev parent reply other threads:[~2018-01-04 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-01-03 Thomas Petazzoni
2018-01-04 14:42 ` Romain Naour [this message]
2018-01-05 17:53 ` Matthew Weber
2018-01-05 17:56 ` Matthew Weber
2018-01-05 20:57 ` Matthew Weber
2018-01-07 22:16 ` Romain Naour
2018-01-07 22:20 ` Thomas Petazzoni
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=12466b9b-4377-b65c-bdb7-c76b136fc3ef@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox