Re: Missing kernelci bot emails?
Will Deacon <[email protected]> Fri, 31 Jul 2026 13:35:12 +0100
| Newsgroups | dev.linux.lists.kernelci |
|---|---|
| Message-ID | <[email protected]> |
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