KernelCI Dashboard Report - August 12 - September 01, 2025
Marcelo Robert Santos <[email protected]> Thu, 4 Sep 2025 16:15:05 -0300
| Newsgroups | dev.linux.lists.kernelci |
|---|---|
| Message-ID | <CAMVAkEs2QXM+O_fEphSUp+-y+zkOVQdnK+4UxYYbnPYSwW-+vQ@mail.gmail.com> |
Hello everyone,
In the past weeks, we have been working on some utility and
configuration changes and because of that we weren’t able to send this
report as frequently as we would like to. Either way, our work is
still strong and we have plenty of updates to report. And with a
better pipeline to deploy our features, we should be able to launch
updates at a better pace in the future.
Here are the changes in the last weeks:
## Docs
- A contributing file is now available, offering guidance for anyone
that is interested on how to contribute to the KernelCI Dashboard.
Thanks to @WilsonNet. [1]
## Improvements
- The endpoints for retrieving builds, boots or tests from a tree now
also have the structure of
api/tree/{tree_name}/{git_branch}/{git_hash_or_tag} followed by
/builds, /boots or /tests. [2]
- The help text for the group_size parameter in the tree-report
endpoint has been improved. [3]
- The cards in the tree and hardware details pages are now ordered
first by fail count, and second alphabetically. This allows users to
see which architecture, configuration, and hardware have the most
failures - Thanks to @giubrocchi. [4]
- Kicking off some UI improvements for a mobile layout, the cards on
tree and hardware detail pages have been refactored to be more
consistent across sizes. [5]
- A better padding was added to the “no issues” message on the issues
card for tree details - Thanks to @khanheric2003. [6]
- In order to allow for a better visibility of pass/fails, the
integration and unit tests on Github’s CI were split, now running
separately. [7]
## Bugfixes
- A few endpoints have long processing, which was expected but there
was a short timeout in the way, preventing them from returning
correctly. The timeout has now been increased. [8]
- In the issue listing, if an applied filter returned 0 results it
would incur an error. This was caused by a query that didn’t need to
be run in this situation, and was fixed. [9]
- The commit selector for the trees on the hardware details page had
repeated commits for some trees. Also, the commit history graph was
breaking if the hardware is a test platform. Both of these were fixed.
[10]
## Notifications
- When running the notifications command, it is possible to skip
reports that have already been sent. [11]
- The checkout email notification now includes a summary of the build
issues, showing new issues and reporting the amount of existing ones.
This has also been reflected in the tree-report endpoint. [12]
## Database
- The script for moving data between the old and new database has been
improved with origin and related-data-only options. [13]
## Docker
- The docker environment variables were moved to specific env files,
so that they can be saved, shared, and changed without changing the
docker compose file itself - Thanks to @nuclearcat. [14]
## Future Changes
We are almost ready to move over from kcidb on Google Cloud to a new
database on Azure, only some final configurations are needed. And
again, just remembering submissions sent through the REST API are all
archived, so no data will be lost. On another note, we are starting to
give some attention to a better experience on smaller screens,
starting with some changes to the mobile UI. After we finish the
database transition, we are looking forward to starting to improve its
schema and performance.
## References
[1] https://github.com/kernelci/dashboard/issues/1293
[2] https://github.com/kernelci/dashboard/issues/1309
[3] https://github.com/kernelci/dashboard/issues/1405
[4] https://github.com/kernelci/dashboard/issues/1261
[5] https://github.com/kernelci/dashboard/issues/1411
[6] https://github.com/kernelci/dashboard/issues/1427
[7] https://github.com/kernelci/dashboard/issues/1402
[8] https://github.com/kernelci/dashboard/issues/1392
[9] https://github.com/kernelci/dashboard/issues/1381
[10] https://github.com/kernelci/dashboard/pull/1446
[11] https://github.com/kernelci/dashboard/issues/1216
[12] https://github.com/kernelci/dashboard/issues/1394
[13] https://github.com/kernelci/dashboard/issues/1401
[14] https://github.com/kernelci/dashboard/pull/1399