From: Philippe Gerum <rpm@xenomai.org>
To: Tobias Schaffner <tobias.schaffner@siemens.com>
Cc: xenomai@lists.linux.dev, jan.kiszka@siemens.com
Subject: Re: [PATCH xenomai-images 0/3] longterm EVL testing under load
Date: Wed, 15 Jul 2026 12:23:43 +0200 [thread overview]
Message-ID: <87zezslff4.fsf@xenomai.org> (raw)
In-Reply-To: <20260715092822.223712-1-tobias.schaffner@siemens.com> (Tobias Schaffner's message of "Wed, 15 Jul 2026 11:28:19 +0200")
Tobias Schaffner <tobias.schaffner@siemens.com> writes:
> Hi all,
>
> This series introduces EVL test runs with additional stress applied via
> stress-ng, as well as long-term testing. Along the way, I also updated the
> long-term kernel under test from 6.12 to 6.18.
>
> Please note:
> * The clock-timer-periodic test currently fails as soon as stress is
> applied. I proposed "tests: skip clock-timer-periodic on virtual targets"
> to address this.
> * On the Raspberry Pi 4, even the 3-minute test exceeds the latency
> threshold with debugging disabled:
> latency threshold is exceeded (150000 >= 163.951), aborting.
> https://gitlab.com/Xenomai/xenomai-images/-/jobs/15353275174
We should not exceed 80 µs or so on pi4.
--
Philippe.
next prev parent reply other threads:[~2026-07-15 10:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 9:28 [PATCH xenomai-images 0/3] longterm EVL testing under load Tobias Schaffner
2026-07-15 9:28 ` [PATCH xenomai-images 1/3] ci: use stress-ng to stress EVL tests Tobias Schaffner
2026-07-15 13:00 ` Florian Bezdeka
2026-07-15 18:47 ` Tobias Schaffner
2026-07-15 9:28 ` [PATCH xenomai-images 2/3] ci: Update for longterm test runs from 6.12 to 6.18 Tobias Schaffner
2026-07-15 9:28 ` [PATCH xenomai-images 3/3] ci: add long-term EVL CI test pipeline Tobias Schaffner
2026-07-15 10:19 ` [PATCH xenomai-images 0/3] longterm EVL testing under load Jan Kiszka
2026-07-15 10:46 ` Tobias Schaffner
2026-07-15 10:23 ` Philippe Gerum [this message]
2026-07-15 12:38 ` Philippe Gerum
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=87zezslff4.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=jan.kiszka@siemens.com \
--cc=tobias.schaffner@siemens.com \
--cc=xenomai@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.