From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [buildroot-test] scripts/autobuild-run: extend timeout from 120 to 180 minutes
Date: Sat, 1 Jan 2022 21:09:57 +0100 [thread overview]
Message-ID: <20220101210957.0fde77e5@windsurf> (raw)
In-Reply-To: <9c4d8993-46b2-8f1a-6aa3-bdd9957b783c@benettiengineering.com>
Hello,
On Sat, 1 Jan 2022 16:10:09 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> > Please
> > note that this HUNG_BUILD_TIMEOUT value is the per-step timeout: it
> > verifies that one step of one particular package doesn't take more than
> > 120 minutes.
>
> Ah, I thought the entire build, but that makes no sense since some build
> can take way more than 2 hours.
There used to be a global timeout for the build, but we had false
positives when really large configurations were built. Due to this,
commit 86892c63f754b4f6c9a4a517fde30160127b3506 change to a more fine
grained timeout: we monitor the file build-time.log (which gets
appended everytime the step of a package starts or ends), and we time
out after HUNG_BUILD_TIMEOUT minutes if that file hasn't changed;
> > Did you identify that the python-uvloop and python-lxml packages really
> > took more than 2 hours to build? I did see at
> > http://autobuild.buildroot.net/?status=TIMEOUT those timeouts dating
> > back from ~November. Did you reproduce the issue, and verified that the
> > build indeed completes at some point? In general, if a simple package
> > such as python-uvloop or python-lxml takes more than 2 hours to build,
> > it means that the compiler (or linker) has gone crazy in an infinite
> > loop, and the build will in fact never finish.
>
> It was only my suspicious as specified in commit log. I couldn't
> reproduce it and I thought it was due to the autobuilder's host.
>
> And yes, now that I know it's a per-step timeout it doesn't make sense
> at all for such little packages.
Yes, for such small packages, it clearly hints at a compiler/linker bug
that stays stuck in an infinite loop.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-01 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 23:14 [Buildroot] [buildroot-test] scripts/autobuild-run: extend timeout from 120 to 180 minutes Giulio Benetti
2022-01-01 10:50 ` Thomas Petazzoni
2022-01-01 15:10 ` Giulio Benetti
2022-01-01 20:09 ` Thomas Petazzoni [this message]
2022-01-01 20:43 ` Giulio Benetti
-- strict thread matches above, loose matches on Subject: below --
2021-09-27 18:50 Giulio Benetti
2021-09-30 23:15 ` Giulio Benetti
2021-09-26 23:26 Giulio Benetti
2021-09-30 23:15 ` Giulio Benetti
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=20220101210957.0fde77e5@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
/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