From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] autobuilder flock hangs
Date: Thu, 16 Aug 2018 11:10:59 +0200 [thread overview]
Message-ID: <20180816111059.3a7f1b59@windsurf> (raw)
In-Reply-To: <1a4b53ec-1ed3-7770-3a65-8d4f4f596918@mentor.com>
Hello,
On Mon, 13 Aug 2018 11:18:10 -0700, Hollis Blanchard wrote:
> flock was hanging. I don't know why; have you experienced anything like
> that?
>
> I deleted the directories and subsequent manual dl-wrapper invocations
> succeeded, so I restarted the builder.
This happened again:
http://autobuild.buildroot.net/results/ddb/ddbc96b24017f2a2b06c6091dea3e19520bf2dd1/
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-16 9:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-12 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-11 Thomas Petazzoni
2018-08-12 20:36 ` [Buildroot] Analysis of build " Thomas Petazzoni
2018-08-13 11:33 ` Romain Naour
2018-08-13 14:15 ` Matthew Weber
2018-08-13 22:43 ` Arnout Vandecappelle
2018-08-14 2:21 ` Matthew Weber
2018-08-13 14:36 ` Matthew Weber
2018-08-13 15:30 ` Matthew Weber
2018-08-13 18:10 ` [Buildroot] host-libselinux atomics with GCC 4.4 Hollis Blanchard
2018-08-13 18:25 ` Matthew Weber
2018-08-13 19:43 ` Hollis Blanchard
2018-08-16 9:43 ` Thomas Petazzoni
2018-08-13 18:18 ` [Buildroot] autobuilder flock hangs Hollis Blanchard
2018-08-13 21:18 ` Thomas Petazzoni
2018-08-13 21:28 ` Yann E. MORIN
2018-08-16 9:10 ` Thomas Petazzoni [this message]
2018-08-24 7:02 ` [Buildroot] Autobnuilders timeouts [was: Re: autobuilder flock hangs] Yann E. MORIN
2018-08-24 23:45 ` Hollis Blanchard
2018-08-25 13:05 ` Yann E. MORIN
2018-09-27 17:18 ` Hollis Blanchard
2018-08-24 23:54 ` Matthew Weber
2018-08-25 13:31 ` Yann E. MORIN
2018-08-25 13:58 ` Romain Naour
2018-08-26 13:00 ` Matthew Weber
2018-08-27 16:31 ` Julien Boibessot
2018-08-28 9:03 ` 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=20180816111059.3a7f1b59@windsurf \
--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