From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-01-03
Date: Sun, 7 Jan 2018 23:20:54 +0100 [thread overview]
Message-ID: <20180107232054.750b6a84@windsurf> (raw)
In-Reply-To: <cbf92a23-f475-b9e4-a71c-d3edf95e46da@gmail.com>
Hello,
On Sun, 7 Jan 2018 23:16:08 +0100, Romain Naour wrote:
> Here is the instance log for the following build:
>
> [Fri, 05 Jan 2018 11:35:51] INFO: build started
> [Sat, 06 Jan 2018 03:19:51] INFO: build hung
> [Sat, 06 Jan 2018 03:19:51] INFO: file mtime:[02:19:47]
> [Sat, 06 Jan 2018 03:19:51] INFO: timeNow:[03:19:51]
> [Sat, 06 Jan 2018 03:19:51] INFO: file mtime(second read):[02:19:47]
> [Sat, 06 Jan 2018 03:19:51] INFO: build timed out [-9]
>
> http://autobuild.buildroot.net/results/ca7/ca70ce7cdbdb834bf448bcb168de9d5bba9f9178/build-end.log
The build-time.log ends with:
1515201587:start:extract : host-ti-cgt-pru
And 1515201587 is:
Saturday, January 6, 2018 2:19:47 AM GMT+01:00
I.e, it does match the mtime of 02:19:47.
So it really seems like this extract step was stuck for an hour.
To me, this log shows that the hung detector worked as expected, and
that for this specific situation, the problem is that the extract step
of host-ti-cgt-pru never completes.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2018-01-07 22:20 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
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 [this message]
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=20180107232054.750b6a84@windsurf \
--to=thomas.petazzoni@free-electrons.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