From: Stefan Agner <stefan@agner.ch>
To: openembedded-core@lists.openembedded.org
Cc: luka.pivk@gmail.com
Subject: Lock external repository in custom FSTYPE
Date: Mon, 29 Oct 2018 13:31:38 +0100 [thread overview]
Message-ID: <77e2fb99554339ea31caf60700a1595f@agner.ch> (raw)
Hi,
We use meta-updater, which has a custom FSTYPE to build a OSTree
repository. We share that repository across multiple bitbake executions.
The underlying OSTree tools lock the OSTree repository before trying to
interact, and if it fails ("error: Locking repo exclusive failed:
Resource temporarily unavailable") then the complete build fails (see
also https://github.com/advancedtelematic/meta-updater/issues/412).
Now I'd rather prefer that two bitbake tasks would serialize the access
to the OSTree repository. Is there a mechanism in bitbake to lock (and
wait) for the repository to be not in use?
We tried using bb.utils.lockfile, but the task is written in shell. Also
inline Python would not work since locking/unlocking need to be done
within one Python script as far as I understand.
--
Stefan
next reply other threads:[~2018-10-29 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 12:31 Stefan Agner [this message]
2018-10-29 13:01 ` Lock external repository in custom FSTYPE Khem Raj
2018-11-01 22:27 ` Stefan Agner
2018-11-02 8:16 ` Stefan Agner
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=77e2fb99554339ea31caf60700a1595f@agner.ch \
--to=stefan@agner.ch \
--cc=luka.pivk@gmail.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox