public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: henning.schild@siemens.com, adriaan.schmidt@siemens.com
Subject: Re: [PATCH v4 0/2] Improve handling of ISAR_RELEASE_CMD
Date: Tue, 16 Nov 2021 21:09:50 +0300	[thread overview]
Message-ID: <c10f0fa1-9f28-e3a4-a1b9-24b6253e4ddb@ilbers.de> (raw)
In-Reply-To: <20211104110507.2358692-1-felix.moessbauer@siemens.com>

04.11.2021 14:05, Felix Moessbauer wrote:
> Changes since v3:
>
> - add API changelog entry
>
> Changes since v2:
>
> - fix bug in update_etc_os_release
> - Strip newlines from ISAR_RELEASE_CMD
>
> Changes since v1:
>
> - remove obsolete get_build_id function
>
> Felix Moessbauer (2):
>    always invoke ISAR_RELEASE_CMD to invalidate downstream tasks on
>      change
>    Ensure generation of /etc/os-release is idempotent
>
>   RECIPE-API-CHANGELOG.md                       | 13 ++++++++
>   meta/classes/image-postproc-extension.bbclass |  6 ++--
>   meta/classes/image.bbclass                    | 32 ++++++++++---------
>   meta/classes/rootfs.bbclass                   |  2 +-
>   4 files changed, 34 insertions(+), 19 deletions(-)
>
This patchset fails on CI with the following error:

NOTE: Running task 171 of 173 
(mc:qemuamd64-bullseye:/meta-isar/recipes-core/images/isar-image-base.bb:do_image)
ERROR: When reparsing 
mc:qemuamd64-bullseye:/meta-isar/recipes-core/images/isar-image-base.bb:do_rootfs_postprocess,
the basehash value changed from 
16a8399888ee56cde01e3fd03937f3847e0f945712e4183858f58527bebc58a7 to
b01a488185cef694cbc7e29bf07d0cf9547355f6f00c79f664491eb058b91632. The 
metadata is not deterministic and this needs to be fixed.

-- 
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov


  parent reply	other threads:[~2021-11-16 18:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 11:05 Felix Moessbauer
2021-11-04 11:05 ` [PATCH v4 1/2] always invoke ISAR_RELEASE_CMD to invalidate downstream tasks on change Felix Moessbauer
2021-11-04 11:05 ` [PATCH v4 2/2] Ensure generation of /etc/os-release is idempotent Felix Moessbauer
2021-11-04 13:12 ` [PATCH v4 0/2] Improve handling of ISAR_RELEASE_CMD Henning Schild
2021-11-16 18:09 ` Anton Mikanovich [this message]
2021-11-17 10:45   ` Moessbauer, Felix
2021-11-17 13:05     ` Anton Mikanovich
2021-11-17 15:57       ` Moessbauer, Felix
2021-11-17 16:39         ` Baurzhan Ismagulov
2021-11-22 15:28         ` Anton Mikanovich
2021-11-24  9:30           ` Schmidt, Adriaan
2021-11-24 10:15             ` Moessbauer, Felix
2021-11-24 11:25               ` Jan Kiszka
2021-11-24 11:54                 ` Anton Mikanovich
2021-11-24 12:11               ` Henning Schild
2021-11-29  9:09                 ` Anton Mikanovich
2021-11-29  9:50                   ` Henning Schild
2021-11-29  9:55                     ` Anton Mikanovich
2021-11-29 13:04                   ` Anton Mikanovich
2021-11-29 13:18                     ` Henning Schild
2021-11-29 14:20                       ` Anton Mikanovich
2021-11-30 10:03                         ` Moessbauer, Felix
2021-12-01 10:39                           ` Anton Mikanovich
2021-12-02 14:55                           ` Anton Mikanovich
2021-12-03  9:51                             ` Moessbauer, Felix
2021-11-24 11:53             ` Anton Mikanovich
2021-11-24 12:35             ` Henning Schild
2021-11-24 12:52               ` Anton Mikanovich
2021-11-17 16:54       ` Henning Schild
2021-11-18  8:36         ` 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=c10f0fa1-9f28-e3a4-a1b9-24b6253e4ddb@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=adriaan.schmidt@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=henning.schild@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