From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Mikko Rapeli <mikko.rapeli@linaro.org>
Cc: Michal Sieron <michalwsieron@gmail.com>,
bitbake-devel@lists.openembedded.org,
Tomasz Dziendzielski <tomasz.dziendzielski@gmail.com>,
Mateusz Marciniec <mateuszmar2@gmail.com>
Subject: Re: [bitbake-devel] [PATCH] bitbake: Add task timeout support
Date: Thu, 25 May 2023 12:59:08 +0200 [thread overview]
Message-ID: <CANNYZj8HQvGOFCx_jLXPBhcSCgGdF5j8=oBvKFU42btQoZNT=w@mail.gmail.com> (raw)
In-Reply-To: <ZG88JxkZkP4z3kR5@nuoska>
I tend to agree, if the problem is that some server is too slow, or
unresponsive, this does not solve the problem. If you want to forcibly
terminate stuff (which is still not a good idea - you should look into
why something 'doesn't work properly', not work around it), you can
terminate the whole bitbake process instead.
Alex
On Thu, 25 May 2023 at 12:45, Mikko Rapeli <mikko.rapeli@linaro.org> wrote:
>
> Hi,
>
> On Thu, May 25, 2023 at 12:21:05PM +0200, Michal Sieron wrote:
> > By setting `BB_TASK_TIMEOUT` you can control timeout of for tasks.
> > Using flags `BB_TASK_TIMEOUT[do_mytask]` you can override timeout
> > settings for specific tasks.
> >
> > This is especially useful when some server doesn't work properly and
> > `do_fetch` task takes too long. We may want to kill it early instead
> > of waiting for a fetch that won't happen.
>
> Is the problem related some tools and network protocols? Which?
>
> An alternative would be to configure the tool (git, svn, curl etc) specific
> settings, or even the default socket timeouts on the running system.
>
> I've seen this kind of problems too, but I'm not sure this task timeout is the
> correct way to solve it. Time is too relative :)
>
> Cheers,
>
> -Mikko
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#14807): https://lists.openembedded.org/g/bitbake-devel/message/14807
> Mute This Topic: https://lists.openembedded.org/mt/99127010/1686489
> Group Owner: bitbake-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/bitbake-devel/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2023-05-25 10:59 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 [this message]
2023-05-25 11:44 ` Tomasz Dziendzielski
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='CANNYZj8HQvGOFCx_jLXPBhcSCgGdF5j8=oBvKFU42btQoZNT=w@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=mateuszmar2@gmail.com \
--cc=michalwsieron@gmail.com \
--cc=mikko.rapeli@linaro.org \
--cc=tomasz.dziendzielski@gmail.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;
as well as URLs for NNTP newsgroup(s).