public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: Re: [RFC] add uuid to schroot folder
Date: Mon, 11 Jul 2022 21:34:54 +0300	[thread overview]
Message-ID: <3bdafbaf-2ed9-46a4-3606-46ac76f99731@ilbers.de> (raw)
In-Reply-To: <20220711183111.3860-1-amikan@ilbers.de>

[-- Attachment #1: Type: text/plain, Size: 748 bytes --]

11.07.2022 21:31, Anton Mikanovich wrote:
> PIDs are not unique across containers.
> When running the build in a container (e.g. the kas container),
> the PID of bitbake is likely the same across multiple simultaneously
> running builds.
>
> This is especially the case for CI runners, where it is common that
> multiple jobs run in parallel.
>
> This patch adds an additional UUID component stored till the end of
> the build in bitbake persistend storage.
>
> Signed-off-by: Anton Mikanovich<amikan@ilbers.de>
> Signed-off-by: Felix Moessbauer<felix.moessbauer@siemens.com>

Here is the version I propose as an alternative to original patch.
Main differences are:
1) placing everything inside bitbake
2) regeneration of UUID on every bitbake run

[-- Attachment #2: Type: text/html, Size: 1554 bytes --]

  reply	other threads:[~2022-07-11 18:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 18:31 Anton Mikanovich
2022-07-11 18:34 ` Anton Mikanovich [this message]
2022-07-12 13:38   ` Moessbauer, Felix
2022-07-13 13:23     ` Anton Mikanovich
2022-07-13 13:52       ` Moessbauer, Felix

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=3bdafbaf-2ed9-46a4-3606-46ac76f99731@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=felix.moessbauer@siemens.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