Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Autobnuilders timeouts [was: Re: autobuilder flock hangs]
Date: Tue, 28 Aug 2018 11:03:43 +0200	[thread overview]
Message-ID: <20180828110343.457a2279@windsurf.home> (raw)
In-Reply-To: <68fc2553-681c-2d7c-8b32-e425073964b6@free.fr>

Hello,

On Mon, 27 Aug 2018 18:31:53 +0200, Julien Boibessot wrote:

> > Matthew, Julien, could you have a look at what is causing those on your
> > autobuilders?  
> 
> I already signaled this problem on BR IRC chan. ;-)
> When occurring, my autobuilder is stuck with a "conftest" process
> consuming 100% of the CPU, indefinitely.
> 
> When building host-libsodium alone, all is fine.
> 
> When it fails with 100% CPU usage I can only kill the process and don't
> see what is happening. I would say this problem is quite recent (3
> months ?).
> 
> What can I do to look further ?

conftest is the typical name of the programs built and run
by ./configure scripts to check/detect whatever they are told to check.
It would be useful to see the contents of the config.log file of
host-libsodium when the problem occurs, to see which particular test is
failing.

Also, is it something you can reproduce with br-reproduce-build
(https://git.buildroot.net/buildroot-test/plain/utils/br-reproduce-build),
using the hash of a build that timed out for you ? Maybe building
host-libsodium alone doesn't exhibit the problem, and it only appears
when a certain set of dependencies has been built prior to
host-libsodium.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-08-28  9:03 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
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 [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=20180828110343.457a2279@windsurf.home \
    --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