From: Tomasz Dziendzielski <tomasz.dziendzielski@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Mikko Rapeli <mikko.rapeli@linaro.org>,
Michal Sieron <michalwsieron@gmail.com>,
bitbake-devel@lists.openembedded.org,
Mateusz Marciniec <mateuszmar2@gmail.com>
Subject: Re: [bitbake-devel] [PATCH] bitbake: Add task timeout support
Date: Thu, 25 May 2023 13:44:53 +0200 [thread overview]
Message-ID: <CAJkqNs2iyuVXRU-Wva+9pC58XixbM5YPC6c8hfgNuDY+9aYaRg@mail.gmail.com> (raw)
In-Reply-To: <CANNYZj8HQvGOFCx_jLXPBhcSCgGdF5j8=oBvKFU42btQoZNT=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
Hello,
let me give some more context on the patch. We use self hosted gerrit and
artifactory (with git-lfs content and tarballs with source code) instances
which tend to be slow sometimes due to some overloads and other reasons. We
have a 3h timeout for the whole build. Now let's assume do_fetch tasks take
already 60 hours instead of 10 minutes. With the timeout solution proposed
by Michał we can detect it quite fast and stop the build job and unblock
the jenkins nodes for other builds or just retry the build in case the
fetch on the second run would take less time. Now without that and with
timeout on the whole bitbake process we're still holding the jenkins node
for another 2-3 hours even though we know this build has no future.
Best regards,
Tomasz Dziendzielski
[-- Attachment #2: Type: text/html, Size: 856 bytes --]
next prev parent reply other threads:[~2023-05-25 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 10:21 [PATCH] bitbake: Add task timeout support Michal Sieron
2023-05-25 10:44 ` [bitbake-devel] " Mikko Rapeli
2023-05-25 10:59 ` Alexander Kanavin
2023-05-25 11:44 ` Tomasz Dziendzielski [this message]
2023-05-25 12:00 ` Alexander Kanavin
2023-05-25 12:13 ` Tomasz Dziendzielski
2023-05-25 12:21 ` Alexander Kanavin
2023-05-25 12:35 ` Tomasz Dziendzielski
2023-05-25 12:57 ` Mikko Rapeli
2023-06-05 11:46 ` Michal Sieron
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=CAJkqNs2iyuVXRU-Wva+9pC58XixbM5YPC6c8hfgNuDY+9aYaRg@mail.gmail.com \
--to=tomasz.dziendzielski@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=mateuszmar2@gmail.com \
--cc=michalwsieron@gmail.com \
--cc=mikko.rapeli@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).