From: Will Deacon <will@kernel.org>
To: Alan Zanoni Peixinho <alan.peixinho@profusion.mobi>
Cc: Mark Brown <broonie@kernel.org>,
kernelci@lists.linux.dev, catalin.marinas@arm.com
Subject: Re: Missing kernelci bot emails?
Date: Fri, 31 Jul 2026 13:35:12 +0100 [thread overview]
Message-ID: <amyWgI-SATPT3Kmz@google.com> (raw)
In-Reply-To: <CAKKBm2t15GgkDsYympwXuu-=TkU8NZc0Ej6kyDzrMXMaXEHRDQ@mail.gmail.com>
Hi Alan,
On Thu, Jul 30, 2026 at 04:35:40PM -0300, Alan Zanoni Peixinho wrote:
> Apologies for the delay — I wanted to take a proper look at the
> notifications system first, since it's a part of the KernelCI
> Dashboard I hadn't explored in depth before.
No problem, thank you for looking into it.
> From local testing, the system appears to be working as intended. What
> I did find is that a summary email is only sent when two conditions
> are both met:
> 1. A recent checkout exists. The subscribed branch must have a
> checkout that started between 5 and 29 hours before the daily run. The
> 5-hour delay gives builds and tests time to finish reporting, and only
> the most recent checkout in that window is used.
> 2. At least one test changed state. Looking at the last 7 days, a
> test must show a regression (PASS to FAIL), a fix (FAIL to PASS), or
> unstable behaviour (flapping, or inconclusive results such as ERROR or
> SKIP). If everything is stable, the report is skipped.
>
> Debugging against
> https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git, all
> the tests I can see in the current window are passing with no state
> changes, which is why the notification is being
> skipped. Does that match your expectation — that there simply
> haven't been any status changes recently?
Ah, that would expain it then, thanks. If possible, I would actually
like to receive an email even if the status hasn't changed but the HEAD
commit of the tested branch _has_ changed since last time. That way, I
know that the tests have run without having to poll the dashboard. Is
that possible with the current system?
> There is also a flag to send the summary every day (when we have
> builds) regardless of whether anything changed on test status — we
> already use it for the mainline tree. If you'd prefer that for arm64,
> I'm happy to enable it.
That's a bit noisy; it would be more helpful to have one email each time
I push to the branch.
Cheers,
Will
prev parent reply other threads:[~2026-07-31 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 12:13 Missing kernelci bot emails? Will Deacon
2026-07-30 12:17 ` Mark Brown
2026-07-30 19:35 ` Alan Zanoni Peixinho
2026-07-31 12:35 ` Will Deacon [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=amyWgI-SATPT3Kmz@google.com \
--to=will@kernel.org \
--cc=alan.peixinho@profusion.mobi \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--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 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.