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 11:50:58 +0100 [thread overview]
Message-ID: <20220101115058.0515c8d9@windsurf> (raw)
In-Reply-To: <20210930231424.249681-1-giulio.benetti@benettiengineering.com>
Hello Giulio,
On Fri, 1 Oct 2021 01:14:24 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> During the last months some package started to timeout, but this is not due
> to toolchain infinite loop. I think it's due to the increase of the source
> code files' length and to complexity of toolchains or even slow compiling
> time. For example python-uvloop and python-lxml only take long time to
> build with -Os optimization and this makes it seem a TIMEOUT but it's not.
> So let's extend timeout setting from 120 to 180 minutes to avoid false
> TIMEOUTs.
>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Do you have a specific example where you have seen a failure? 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.
Unless you have a specific example where you have seen this timeout
causing false positives, I'm not really keen on applying such a patch
as it would cause situations where the build is really stuck to be
stuck for 3 hours instead of 2.
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.
Best regards,
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 10:51 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 [this message]
2022-01-01 15:10 ` Giulio Benetti
2022-01-01 20:09 ` Thomas Petazzoni
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=20220101115058.0515c8d9@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 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.