[bitbake-devel] gitsm shared DL_DIR and race conditions

Stefan Agner stefan at agner.ch
Wed Jan 9 13:48:08 UTC 2019


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


More information about the bitbake-devel mailing list