From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Ben Copeland <ben.copeland@linaro.org>
Cc: Denys Fedoryshchenko <denys.f@collabora.com>,
Alan Zanoni Peixinho <alan.peixinho@profusion.mobi>,
kernelci <kernelci@lists.linux.dev>,
kernelci-webdashboard <kernelci-webdashboard@groups.io>,
John Ogness <john.ogness@linutronix.de>
Subject: Re: kernelci test results
Date: Wed, 23 Sep 2026 16:11:02 +0200 [thread overview]
Message-ID: <20260923141102.n8dg59TG@linutronix.de> (raw)
In-Reply-To: <CAL0q8a6RKqmEte6t+NcYX3u60YvJS+q_THcwKcO6YReY310-HQ@mail.gmail.com>
On 2026-09-04 09:44:31 [+0100], Ben Copeland wrote:
> Hi Sebastian,
Hi Ben,
> > > > Later there is the cyclictest invocation, arguments and the result.
> > > > There is no max-value set for the test so it passes. Would there be a
> > > > notification if the test failed and if so, where?
>
> I cannot find any thresholds set, which isn't ideal.
> parse_rt_tests_results.py prints the literal string "pass" for every
> latency line; only cyclictest's return code decides the overall
> result. So a max-value parameter on our side would change nothing
> until the parser learns about thresholds.
Regarding the thresholds. Assuming we agree on a default threshold of
100us.
There is
test-definitions/automated/lib/parse_rt_tests_results.py
which has this piece:
| if int(rawdata["return_code"]) == 0:
| print("{} pass".format(testname))
| else:
| print("{} fail".format(testname))
Would that be the right place for the decision (test passed vs failed)?
If so, we could invoke cyclictest with the '-b' argument passing the max
value for the expected latency and then cyclictest would terminate if
the value is reached with the exit code 2. This is however not entirely
possible with the current binary, there is an outstanding patch
https://lore.kernel.org/linux-rt-users/20260824101852.2237494-1-costa.shul@redhat.com/
to be merged. But other than that… :)
> Ben
Sebastian
next prev parent reply other threads:[~2026-09-23 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 15:43 kernelci test results Sebastian Andrzej Siewior
2026-09-03 18:37 ` Alan Zanoni Peixinho
2026-09-04 5:15 ` Denys Fedoryshchenko
2026-09-04 8:44 ` Ben Copeland
2026-09-15 15:35 ` Sebastian Andrzej Siewior
2026-09-16 21:12 ` Alan Zanoni Peixinho
2026-09-23 14:11 ` Sebastian Andrzej Siewior [this message]
2026-09-15 14:28 ` Sebastian Andrzej Siewior
2026-09-15 14:08 ` Sebastian Andrzej Siewior
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=20260923141102.n8dg59TG@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=alan.peixinho@profusion.mobi \
--cc=ben.copeland@linaro.org \
--cc=denys.f@collabora.com \
--cc=john.ogness@linutronix.de \
--cc=kernelci-webdashboard@groups.io \
--cc=kernelci@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox