From: Marcelo Robert Santos <marcelo.santos@profusion.mobi>
To: kernelci@lists.linux.dev
Cc: kernelci-webdashboard@groups.io
Subject: KernelCI Dashboard Report - October 1 - October 13, 2025
Date: Mon, 13 Oct 2025 17:07:45 -0300 [thread overview]
Message-ID: <CAMVAkEviyZrgPk7NP+tVUc6Nfo1DBbiL=4YWnw2H244FVv5SFA@mail.gmail.com> (raw)
Hello everyone,
In the last sprint we had a couple of changes related to performance
tools, both for the database and the backend as a whole. Apart from
that we also keep having improvements on unit test coverage, frontend
responsiveness, notifications and others. Here are the changes from
the last two weeks:
## Database
- The database indexes are now better defined in our backend. They
were already created in the database with a separate tool, so we just
formalized them in our Django models. [1]
- Some indexes that were created with said tool were not necessary,
and have been removed. [2]
- Along with the index changes, the Django migration router had
allowed for some unnecessary cache tables to be created on Postgres,
so they were also removed. [3]
- We are in progress of denormalizing the treeView, with a better plan
and well defined steps for it. [4]
## Improvements
- A framework for performance tests was added to the repository,
allowing for tests on backend endpoints. [5]
- We are now able to check backend metrics, such as which endpoints
were accessed, how many times, and how long they take to load. [6]
- Backend unit tests coverage was increased, a single folder with many
files made possible for us to increase it to more than 60%. [7]
- Continuing our effort for a more responsive design, we improved the
layout of the data interval information on the hardware details page
for smaller screens. [8]
- In the notifications front, we added a link to the build config
directly in the notification for a quicker check. [9]
- Following the bugfix below, we reorganized some environment
variables for logging without needing to enable debug mode. [10]
## Bugfixes
- Email notifications were being duplicated. This was due to our
staging instance being on debug mode for a little while. [11]
## References
[1] - https://github.com/kernelci/dashboard/issues/1351
[2] - https://github.com/kernelci/dashboard/issues/1539
[3] - https://github.com/kernelci/dashboard/issues/1517
[4] - https://github.com/kernelci/dashboard/issues/1558
[5] - https://github.com/kernelci/dashboard/issues/1529
[6] - https://github.com/kernelci/dashboard/issues/1535
[7] - https://github.com/kernelci/dashboard/issues/1496
[8] - https://github.com/kernelci/dashboard/issues/1431
[9] - https://github.com/kernelci/dashboard/issues/1551
[10] - https://github.com/kernelci/dashboard/issues/1546
[11] - https://github.com/kernelci/dashboard/issues/1540
reply other threads:[~2025-10-13 20:07 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='CAMVAkEviyZrgPk7NP+tVUc6Nfo1DBbiL=4YWnw2H244FVv5SFA@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).