public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Cedric Hombourger <Cedric_Hombourger@mentor.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH] image: acquire lock when running do_cache_base_repo()
Date: Fri, 8 Feb 2019 08:47:28 +0100	[thread overview]
Message-ID: <2f467373-16c4-967a-2c18-8b68bfff6b13@ilbers.de> (raw)
In-Reply-To: <1549559456-916-1-git-send-email-Cedric_Hombourger@mentor.com>

On 2/7/19 6:10 PM, Cedric Hombourger wrote:
> The base repository gets updated as images are built. As multiple
> images may be built concurrently, accesses to the base cache repo
> should be serialized by having do_cache_base_repo acquire the
> following lock file: ${REPO_BASE_DIR}/isar.lock

Applied to the 'next',

Thanks,
Maxim.

> Fixes: https://groups.google.com/forum/#!topic/isar-users/ElRP1h_9m9I
> Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
> ---
>   meta/classes/image.bbclass | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index d8fbfd5..be00817 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -128,6 +128,7 @@ addtask populate_sdk after do_rootfs
>   inherit base-apt-helper
>   
>   do_cache_base_repo[depends] = "base-apt:do_cache_config"
> +do_cache_base_repo[lockfiles] = "${REPO_BASE_DIR}/isar.lock"
>   do_cache_base_repo[stamp-extra-info] = "${MACHINE}-${DISTRO}"
>   
>   do_cache_base_repo() {
> 


-- 
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov

      reply	other threads:[~2019-02-08  7:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 17:10 Cedric Hombourger
2019-02-08  7:47 ` Maxim Yu. Osipov [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=2f467373-16c4-967a-2c18-8b68bfff6b13@ilbers.de \
    --to=mosipov@ilbers.de \
    --cc=Cedric_Hombourger@mentor.com \
    --cc=isar-users@googlegroups.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