From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Alan Zanoni Peixinho <alan.peixinho@profusion.mobi>
Cc: kernelci@lists.linux.dev, kernelci-webdashboard@groups.io,
John Ogness <john.ogness@linutronix.de>
Subject: Re: kernelci test results
Date: Tue, 15 Sep 2026 16:08:58 +0200 [thread overview]
Message-ID: <20260915140858.W5JzUKyx@linutronix.de> (raw)
In-Reply-To: <CAKKBm2t3EoD4cRiBJzLqpE79ehRs+Xs-Ypb5ta3Y7rC=0jjyKA@mail.gmail.com>
On 2026-09-03 15:37:09 [-0300], Alan Zanoni Peixinho wrote:
> Hi Sebastian, I work with the dashboard team, so I hope I am able to help you.
Hi Alan,
> First of all, thanks for using the dashboard, and for taking time to
> write this up. Scenarios like this one are exactly what help us find
> the UX gaps for improvement.
>
> The dashboard is mostly organized around tree checkouts first.
> If i understood it properly you might be able to achieve what you are
> looking for via:
> 1. Selecting a tree (ie stable-rt/v6.6-rt).
> 2. Clicking on the filters button on the right. There we can apply
> filters for configs (defconfig+preempt_rt, etc).
> 3. We click on the tests tab (default tab is for builds).
> 4. On the list of tests you can search for test paths (cyclictest,
> rt-tests, etc).
Oh, okay. This makes things a bit easier.
Now that I clicked next tree and filter the preempt_rt builds I see
"builds", "boots" and "tests". Now clicking below I can get all the
cyclictest results for all the boards.
The confusing part is that "boots" says 0 but then I can download the
complete log for one of the boards where the test did run. So I guess
"boot" is something else here.
> Link for the view:
> https://dashboard.kernelci.org/tree/stable-rt/v6.6-rt/84925bb144f49eb0d5f4c5c29f690b4bbf84903b?df|c|defconfig%2Bpreempt_rt=true&p=t
>
> That list is for that checkout across hardware, so you do not have to
> go board by board. (Unfortunately there is still no search for “this
> test on this device over time” across all trees.)
I see.
> About the other questions.
>
> All the logs presented are the ones that have been submitted via KCI
> submissions, so there might be some missing information when not
> reported.
Okay. What I see that the "kubernetes" seem not to submit anything but
the actual tests do.
> On the topic of notifying on log errors, this is a feature on active
> discussion, to automate notification for first for boots and later for
> test failures as well. Today we only notify registered issues.
>
> We are actually looking for some feedback of dashboard users to help
> us steer on the roadmap for new features, and your help would be much
> appreciated.
Is there something you want me to do?
> Att
> Alan Peixinho
> KernelCI Dashboard Team
Sebastian
prev parent reply other threads:[~2026-09-15 14:09 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
2026-09-15 14:28 ` Sebastian Andrzej Siewior
2026-09-15 14:08 ` Sebastian Andrzej Siewior [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=20260915140858.W5JzUKyx@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=alan.peixinho@profusion.mobi \
--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