From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: CI fails on next due to cachability issues
Date: Wed, 31 Aug 2022 11:58:39 +0000 [thread overview]
Message-ID: <AM9PR10MB48694B8520B30F3DDA9DEBFC89789@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
Hi,
I just want to let you know that the CI is currently failing as the cachability test detected issues.
This is related to aefbe7f which improved the detection of cachability issues.
However, the patch itself is unrelated. It just made the bug visible.
I just spotted that while looking at the BBLAYERS variable that is under discussion on the KAS mailinglist as well.
I'm wondering why we did not spot that earlier.
Working on a fix.
Logs:
[stdlog] 2022-08-30 19:20:50,943 avocado.utils.process DEBUG| [stdout] [1;33m==== issues found in amd64:isar-image-base:rootfs_postprocess (5e919594) ====[0m
[stdlog] 2022-08-30 19:20:50,943 avocado.utils.process DEBUG| [stdout] [0;31m-> path in sources-dir: BBLAYERS = "/builds/ebsy/debian/isar/meta /builds/ebsy/debian/isar/meta-isar "[0m
[stdlog] 2022-08-30 19:20:50,943 avocado.utils.process DEBUG| [stdout] [1;33m==== issues found in amd64:isar-image-base:rootfs_wicenv (1e0c0d47) ====[0m
[stdlog] 2022-08-30 19:20:50,943 avocado.utils.process DEBUG| [stdout] [0;31m-> path in sources-dir: BBLAYERS = "/builds/ebsy/debian/isar/meta /builds/ebsy/debian/isar/meta-isar "[0m
[stdlog] 2022-08-30 19:20:50,944 avocado.utils.process DEBUG| [stdout] [1;33m==== issues found in amd64:isar-image-base:image_wic (3a0614c9) ====[0m
[stdlog] 2022-08-30 19:20:50,944 avocado.utils.process DEBUG| [stdout] [0;31m-> path in sources-dir: BBLAYERS = "/builds/ebsy/debian/isar/meta /builds/ebsy/debian/isar/meta-isar "[0m
Felix
--
Siemens AG, Linux Expert Center
Otto-Hahn-Ring 6, 81739 München, Germany
[-- Attachment #2: Type: text/html, Size: 4037 bytes --]
next reply other threads:[~2022-08-31 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 11:58 Moessbauer, Felix [this message]
2022-09-02 11:50 ` Schmidl, Tobias
2022-09-02 13:07 ` 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=AM9PR10MB48694B8520B30F3DDA9DEBFC89789@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
--to=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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