From: Anton Mikanovich <amikan@ilbers.de>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>,
"Hombourger, Cedric" <cedric.hombourger@siemens.com>
Subject: Re: [RFC 1/1] mark ci tests that need attention
Date: Tue, 16 Dec 2025 09:31:29 +0200 [thread overview]
Message-ID: <020f55c4-f31f-4376-9990-e12040f1f5dc@ilbers.de> (raw)
In-Reply-To: <b0c74663faeb33712fff093bf2f041577ade10fc.camel@siemens.com>
Hello Felix,
12/12/2025 18:58, 'MOESSBAUER, Felix' via isar-users wrote:
> I just noticed, that the test_cross_kselftest is not cross anymore,
> because the kselftest class explicitly disables it via
> ISAR_CROSS_COMPILE = "0". This is a prime example of the test aging
> pattern.
I've just merged the commit:
[PATCH] meta/classes-recipe/linux-kselftest: remove forced
ISAR_CROSS_COMPILE = "0"
so this case is no more exists.
> Monitoring the CI execution time helps to spot slow time increases, as
> well as spikes due to unintended changes (like this one).
> This at least gives an indication.
>
> Felix
>
--
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/020f55c4-f31f-4376-9990-e12040f1f5dc%40ilbers.de.
prev parent reply other threads:[~2025-12-16 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 16:34 'Felix Moessbauer' via isar-users
2025-12-12 16:42 ` 'Jan Kiszka' via isar-users
2025-12-12 16:58 ` 'MOESSBAUER, Felix' via isar-users
2025-12-16 7:31 ` Anton Mikanovich [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=020f55c4-f31f-4376-9990-e12040f1f5dc@ilbers.de \
--to=amikan@ilbers.de \
--cc=cedric.hombourger@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