Hardware details header commits and commit graph diverge
- Dominant language
- Python
- Stars
- 9
- Forks
- 31
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 16
Description
In the hardware details page, there's the header table listing the trees that that hardware appeared, and there are the commits in which it appeared. When a single tree is selected, the commit history graph appears with the count of past commits with that hardware.
The issue is that it is possible that a tree had that hardware for less commits than what is shown in the graph, and users can then use the commit graph to navigate to a commit that has 0 builds, boots and tests with that hardware.
At the same time, it is possible that a hardware appeared in a tree for more commits than what is shown in the graph, making the user only able to navigate through the dropdown of the table and showing no selected commit in the graph.
Example: [Hardware details for rk3399-gru-kevin](https://dashboard.kernelci.org/hardware/rk3399-gru-kevin?et=1749672000&st=1749240000), see that it is only present for one commit of a lot of trees, but appears on more than 6 commits for android/android16-6.12
Contributor guide
Research direction
Start at the hardware details page linked in the issue and compare the selected tree's commit count with the commit history graph for rk3399-gru-kevin. Trace how both counts and navigation targets are produced, then verify that the graph and header table agree and do not navigate to commits with zero builds, boots, or tests for that hardware.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100