From: Stefan Agner <stefan@agner.ch>
To: bitbake-devel@lists.openembedded.org
Subject: gitsm shared DL_DIR and race conditions
Date: Wed, 09 Jan 2019 14:48:08 +0100 [thread overview]
Message-ID: <4e90ed7e8eea81f3f8e3abd072aedaca@agner.ch> (raw)
Hi,
We came across race conditions while fetching a repository using gitsm:
ERROR: aktualizr-native-1.0+gitAUTOINC+d00d1a04cc-7 do_fetch: Fetcher
failure: Fetch command export PSEUDO_DISABLED=1; export
PATH="/workdir/oe/layers/openembedded-core/scripts/native-intercept:/workdir/oe/layers/openembedded-core/scripts:/workdir/oe/tmp/work/x86_64-linux/aktualizr-native/1.0+gitAUTOINC+d00d1a04cc-7/recipe-sysroot-native/usr/bin/x86_64-linux:/workdir/oe/tmp/work/x86_64-linux/aktualizr-native/1.0+gitAUTOINC+d00d1a04cc-7/recipe-sysroot-native/usr/bin:/workdir/oe/tmp/work/x86_64-linux/aktualizr-native/1.0+gitAUTOINC+d00d1a04cc-7/recipe-sysroot-native/usr/sbin:/workdir/oe/tmp/work/x86_64-linux/aktualizr-native/1.0+gitAUTOINC+d00d1a04cc-7/recipe-sysroot-native/usr/bin:/workdir/oe/tmp/work/x86_64-linux/aktualizr-native/1.0+gitAUTOINC+d00d1a04cc-7/recipe-sysroot-native/sbin:/workdir/oe/tmp/work/x86_64-linux/aktualizr-native/1.0+gitAUTOINC+d00d1a04cc-7/recipe-sysroot-native/bin:/workdir/oe/bitbake/bin:/workdir/oe/tmp/hosttools";
export HOME="/home/yocto"; git -c core.fsyncobjectfiles=0 config
submodule.tests/tuf-test-vectors.url
/workdir/downloads/git2/github.com.advancedtelematic.tuf-test-vectors.
failed with exit code 255, output:
error: could not lock config file config: File exists
We share the same DL_DIR located on a NFS across multiple builders. We
are using latest state of the 1.40 branch (thud) of bitbake.
It seems that two git config invocations raced in this case. Is there
locking required in the current gitsm implementation?
--
Stefan
next reply other threads:[~2019-01-09 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 13:48 Stefan Agner [this message]
2019-01-09 15:38 ` gitsm shared DL_DIR and race conditions Mark Hatle
2019-01-09 16:21 ` Stefan Agner
2019-01-09 16:46 ` Mark Hatle
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=4e90ed7e8eea81f3f8e3abd072aedaca@agner.ch \
--to=stefan@agner.ch \
--cc=bitbake-devel@lists.openembedded.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 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.