From: Marcelo Robert Santos <marcelo.santos@profusion.mobi>
To: kernelci@lists.linux.dev
Cc: kernelci-webdashboard@groups.io
Subject: KernelCI Dashboard Report - October 14 - October 27, 2025
Date: Mon, 27 Oct 2025 13:32:29 -0300 [thread overview]
Message-ID: <CAMVAkEsZR04eR4D7BrzViDYi63eZysg4PnBci2Yksx3FuWX_pg@mail.gmail.com> (raw)
Hello everyone,
In the last two weeks we have improved the performance of the
dashboard and paved the way for some more performance changes, apart
from that we also had a couple of bugfixes and improvements. Here are
the changes from our last 2-week sprint:
## Database
- Some hardware listing changes were tested, mainly about materialized
views, and they soon will be finished. [1]
- The Postgres index that was added manually for hardware listing is
now also added in the Django models. [2]
## Improvements
- Our Prometheus + Grafana performance dashboard now allows an
interval-based summary along with all-time metrics. [3]
## Bugfixes
- The backend coverage badge was not showing, but it was fixed and we
are currently at 53% coverage. [4]
- Microsoft’s email notification issue was a matter of not having
data. In order to prevent such issues in the future, its notifications
are now sent to the main mailing list as well. [5]
## Future Changes
We have better plans on how to improve the performance of the slowest
pages in the dashboard. We will still keep track of the coverage tests
and layout responsiveness. And in the future, we are having plans to
add more functionality to labs description and filtering.
## References
[1] - https://github.com/kernelci/dashboard/issues/1568
[2] - https://github.com/kernelci/dashboard/issues/1578
[3] - https://github.com/kernelci/dashboard/issues/1580
[4] - https://github.com/kernelci/dashboard/issues/1534
[5] - https://github.com/kernelci/dashboard/issues/1564
reply other threads:[~2025-10-27 16:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAMVAkEsZR04eR4D7BrzViDYi63eZysg4PnBci2Yksx3FuWX_pg@mail.gmail.com \
--to=marcelo.santos@profusion.mobi \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).