bitbake-devel.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: Michal Sieron <michalwsieron@gmail.com>
To: Mikko Rapeli <mikko.rapeli@linaro.org>
Cc: Tomasz Dziendzielski <tomasz.dziendzielski@gmail.com>,
	Alexander Kanavin <alex.kanavin@gmail.com>,
	bitbake-devel@lists.openembedded.org,
	Mateusz Marciniec <mateuszmar2@gmail.com>
Subject: Re: [bitbake-devel] [PATCH] bitbake: Add task timeout support
Date: Mon, 5 Jun 2023 13:46:55 +0200	[thread overview]
Message-ID: <20230605134655.3b5313d5@elitebook> (raw)
In-Reply-To: <ZG9bKB8yLRMKqZYT@nuoska>

Hi,

On Thu, 25 May 2023 15:57:12 +0300
Mikko Rapeli <mikko.rapeli@linaro.org> wrote:

> git uses curl, can't we shorten the timeouts or even add retries
> there? Maybe even specific ones for the lfs support?
> 
> I've also seen a lot of problematic artifactory and gerrit instances,
> in addition to maven, npm etc...

I checked this and couldn't find any environment variables that would
control timeout for the whole operation.

The only solution I found (which doesn't require patching/recompiling)
was using previously mentioned timeout command like so:

```
FETCHCMD_git = "git \
    -c core.fsyncobjectfiles=0 \
    -c filter.lfs.clean='/usr/bin/timeout 300 git-lfs clean -- %f' \
    -c filter.lfs.smudge='/usr/bin/timeout 300 git-lfs smudge -- %f' \
    -c filter.lfs.process='/usr/bin/timeout 300 git-lfs filter-process' \
"
```

You can of course put those settings in your gitconfig file instead.

However, this method is not so nice, as when the fetch task ends, and
prints error message from git, we get "fatal: the remote end hung up
unexpectedly", which doesn't really explain what went wrong.

Michal


      reply	other threads:[~2023-06-05 11:47 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
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 [this message]

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=20230605134655.3b5313d5@elitebook \
    --to=michalwsieron@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=mateuszmar2@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).