From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: "Moessbauer,
Felix (T RDA IOT SES-DE)" <felix.moessbauer@siemens.com>,
"Schmidt,
Adriaan (T RDA IOT SES-DE)" <adriaan.schmidt@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH v4 0/2] Improve handling of ISAR_RELEASE_CMD
Date: Mon, 29 Nov 2021 14:18:06 +0100 [thread overview]
Message-ID: <20211129141806.7fcc0fd2@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <bf47ec65-c8db-63b6-f4ca-cf409dca4b4f@ilbers.de>
Am Mon, 29 Nov 2021 16:04:42 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:
> 29.11.2021 12:09, Anton Mikanovich wrote:
> > 24.11.2021 15:11, Henning Schild wrote:
> >>
> >>>> An alternative could be "/bin/su -" instead of userspec. (but
> >>>> userspec is a pretty widely used pattern)
> >>>>
> >>>> Henning
> >>>>
> > I've tried to use `su -`: Jenkins got the correct env and at least
> > started building, but now fails on RebuildTest with hash diff issue.
> > This test case just changes dpkg-base.bbclass and rebuilds one
> > target.
> >
> > Can't reproduce the issue locally (out of CI) for now.
> > Will try to obtain the real hashes diff from CI.
> >
> It was caused by the change IMAGE_BUILD_ID from 'v0.7-537-g6085d11'
> to 'v0.7-537-g6085d11-dirty' which sounds reasonable.
> Was this case (change of source, then rebuild) actually tested?
>
Well that is to expect! I guess that patch did pass our gitlab based
CI, but i do not know.
Please give more details on the failure you see. "hash diff issue" ...
Otherwise we will be in the "works for me, vs have you tried turning it
off and on again" business.
Henning
next prev parent reply other threads:[~2021-11-29 13:18 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
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 [this message]
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=20211129141806.7fcc0fd2@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=ibr@ilbers.de \
--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