From: "'Alexander Heinisch' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: Detect multiple executions
Date: Fri, 13 Dec 2024 15:07:07 -0800 (PST) [thread overview]
Message-ID: <e3883934-225b-4843-afc6-19e8bf81dad9n@googlegroups.com> (raw)
In-Reply-To: <bb569992-396a-47f7-9a98-d56de8ed7f56n@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1289 bytes --]
Hi Stephen,
The dependency on the target image is set here [1].
Basically what you need to do is set `INSTALLER_TARGET_IMAGE ` and
`INSTALLER_TARGET_MC` (only if you provide your own multiconfig) right.
You can find an example on how to set that here [2].
[1] https://github.com/ilbers/isar/blob/master/meta-isar/classes/installer-add-rootfs.bbclass#L52C38-L52C52
[2] https://github.com/ilbers/isar/blob/master/kas/image/isar-image-installer.yaml
How exactly does the race condition manifest?
Are you using the upstream isar multiconfigs for the installer?
BR Alexander
Stephen Ecker schrieb am Freitag, 13. Dezember 2024 um 19:40:34 UTC+1:
can someone help me understand how I'm supposed to make the installer
depend on the base image's completion?
after poking through the code, it looked like this would be accomplished by
setting INSTALLER_TARGET_IMAGE to my base image target, but I'm still
getting race conditions
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/e3883934-225b-4843-afc6-19e8bf81dad9n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1919 bytes --]
prev parent reply other threads:[~2024-12-13 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 18:40 Stephen Ecker
2024-12-13 23:07 ` 'Alexander Heinisch' via isar-users [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=e3883934-225b-4843-afc6-19e8bf81dad9n@googlegroups.com \
--to=isar-users@googlegroups.com \
--cc=alexander.heinisch@siemens.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