From: "Schmidl, Tobias" <tobiasschmidl@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Moessbauer, Felix" <felix.moessbauer@siemens.com>
Cc: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: Re: CI fails on next due to cachability issues
Date: Fri, 2 Sep 2022 11:50:30 +0000 [thread overview]
Message-ID: <d285c8b4a4237baa81d0def6c6abdb37b559534d.camel@siemens.com> (raw)
In-Reply-To: <AM9PR10MB48694B8520B30F3DDA9DEBFC89789@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>
Hi Felix,
Am Mittwoch, dem 31.08.2022 um 11:58 +0000 schrieb Moessbauer, Felix:
> 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.
>
I've just tried to execute `scripts/ci_build.sh -q -f -d -n` based on
current next, with the following result:
```
/home/schtobia/projects/isar/isar-minimal-layer/isar/testsuite/citest.py:CcacheTest.test_ccache_rebuild: FAIL
/home/schtobia/projects/isar/isar-minimal-layer/isar/testsuite/citest.py:CrossTest.test_cross: FAIL
/home/schtobia/projects/isar/isar-minimal-layer/isar/testsuite/citest.py:RebuildTest.test_rebuild: FAIL
/home/schtobia/projects/isar/isar-minimal-layer/isar/testsuite/citest.py:SdkTest.test_sdk: FAIL
/home/schtobia/projects/isar/isar-minimal-layer/isar/testsuite/citest.py:SstateTest.test_sstate: FAIL
```
Might this be related?
Kind regards,
Tobias
next prev parent reply other threads:[~2022-09-02 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 11:58 Moessbauer, Felix
2022-09-02 11:50 ` Schmidl, Tobias [this message]
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=d285c8b4a4237baa81d0def6c6abdb37b559534d.camel@siemens.com \
--to=tobiasschmidl@siemens.com \
--cc=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