All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Issue with host-erlang-rebar causing timeouts
Date: Wed, 27 May 2015 23:18:11 +0200	[thread overview]
Message-ID: <55663493.1040500@mind.be> (raw)
In-Reply-To: <20150521220438.624c6697@free-electrons.com>

On 05/21/15 22:04, Thomas Petazzoni wrote:
> Johan,
> 
> On Thu, 21 May 2015 21:47:26 +0200, Thomas Petazzoni wrote:
> 
>> Maybe I should set up a cronjob that checks every minute if we are in
>> this situation, and send me an e-mail, so that maybe I can catch the
>> situation while it's happening, and see a bit more what's going on. I
>> don't really have better ideas :/
> 
> Turns out that right after sending this e-mail, I checked, and one of
> the build was stuck exactly in this situation. The process tree is like
> this:
> 
> 23332 pts/5    S+     0:01  |       \_ python ../buildroot-test/scripts/autobuild-run -c autobuild-run.conf
> 23969 pts/5    S      0:00  |       |   \_ timeout 28800 make O=/ssd1/thomas/autobuild/instance-2/output -C instance-2/buildroot BR2_DL_DIR=/ssd1/thomas/autobuild/instance-2/dl BR2_JLEVE
> 23970 pts/5    T      0:19  |       |       \_ make O=/ssd1/thomas/autobuild/instance-2/output -C instance-2/buildroot BR2_DL_DIR=/ssd1/thomas/autobuild/instance-2/dl BR2_JLEVEL=4
                 ^
 This means that the 'make' instance either got a SIGSTOP or ptrace(). Is there
some administrative process running on that machine that is doing something
funky with it? Or is it the autobuild-run script that is sending some signal?


> 10928 pts/5    Z      0:00  |       |           \_ [bash] <defunct>
> 
> So basically, the Buildroot "make" invocation only has one child
> process: a bash process that is defunct. This instance is really stuck
> in the ./bootstrap call:

 No it's not, bootstrap is finished already, but the stopped make hasn't reaped
it yet. Actually, even the make has finished already...

> 
> make[1]: Entering directory '/ssd1/thomas/autobuild/instance-2/output/build/host-erlang-rebar-2.5.1'
> ./bootstrap
> [nothing else]

...but somehow the output of that finished make has not yet ended up in the log
file...

 Mysterious...


> 
> I tried running the exact make command that builds host-erlang-rebar in
> a terminal, inside the build directory of this build, and it worked
> perfectly fine. So even more puzzled.

 Have you tried running it within the timeout? Maybe that one is doing SIGSTOP
or ptrace() for some reason...

 Regards,
 Arnout

> 
> I see however that 'bootstrap' tries to play with the hg and git VCS to
> get a commit reference. Maybe this is failing for some reason?
> 
> Any other idea?
> 
> Thomas
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2015-05-27 21:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 19:21 [Buildroot] Issue with host-erlang-rebar causing timeouts Thomas Petazzoni
2015-05-21 19:47 ` Thomas Petazzoni
2015-05-21 20:04   ` Thomas Petazzoni
2015-05-27 21:18     ` Arnout Vandecappelle [this message]
2015-08-10 13:10       ` Johan Oudinet
2015-08-19 21:02       ` Thomas Petazzoni
2015-08-20 21:31         ` Thomas Petazzoni
2015-08-21 15:52           ` Arnout Vandecappelle

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=55663493.1040500@mind.be \
    --to=arnout@mind.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.