Replies: 15 comments 11 replies
-
Some initial user stories with suggestions on how to address them: A kernel developer has sent a patch which caused a regression A maintainer is getting a branch ready for the next merge window An OEM or SoC vendor needs to upgrade their kernel or move to upstream Regular visitors who want to know how the kernel is doing |
Beta Was this translation helpful? Give feedback.
-
Stable kernel maintainer wants to know about a series of patches for a new release candidate:
Ideally, an email would be sent automatically replying to the stable review thread with a |
Beta Was this translation helpful? Give feedback.
-
Kernel / subsystem maintainer wants to know
|
Beta Was this translation helpful? Give feedback.
-
On 19/10/2020 23:10, Nick Desaulniers via groups.io wrote:
|
Beta Was this translation helpful? Give feedback.
-
On 21/10/2020 07:39, Corentin Labbe wrote:
|
Beta Was this translation helpful? Give feedback.
-
From @lag-linaro:
This shows how a maintainer can have a "short" loop with reduced coverage but fast feedback within some minutes, and then a "medium" loop with more coverage and feedback within 1h or so. |
Beta Was this translation helpful? Give feedback.
-
When developers get sent a bisection report, or when they find an issue in general, they may not have the platform at their disposal to reproduce or debug the issue. Having the ability for developers to re-run the automated tests with a patch, or some arbitrary kernel branch and to configure how to build the kernel (i.e. debug options...) would make this possible. Ideally, arbitrary commands or even an interactive session on the test platform would also help but that may be much harder to enable in an automated test system. Here's an example of how this was done by hand, with the intermediate of jobs run on kernelci.org as requested by the developer: |
Beta Was this translation helpful? Give feedback.
-
For the Lab-Operators it has always been a good way to present The current interface is missing the old per lab views.
|
Beta Was this translation helpful? Give feedback.
-
Did this collection of userstories result in any forward discussions or future plans on the project jet? |
Beta Was this translation helpful? Give feedback.
-
From Theodore Ts'O:
|
Beta Was this translation helpful? Give feedback.
-
Not sure if it's the right place for wishing for features. Anyway, for realtime testing, the currently most used approach is to run some workload in the background and run cyclictest to measure the thread wakeup latency. The normal criteria to decide the test passed is the largest observed latency. Though it's not possible to know upfront the highest value to be expected. So it's more a trail and error thing and look at historic data. So it would be really handy to have a graph which plots the trend of observed max latency values for a given board (this is really hardware dependent). But also histograms are of interest (e.g. is the distribution changing over time?) While this is not a hard criteria for good/bad it helps to figure if the system performance is generation over time. (over several kernel releases). So it would be really handy to have builtin support to visualize trends and histograms. See also: |
Beta Was this translation helpful? Give feedback.
-
Not sure if I'm late to this party :D , but in terms of user stories/ wishlist I would add:
Thanks, |
Beta Was this translation helpful? Give feedback.
-
Forking @gctucker's discussion above:
I think the size of the kernel is a pretty niche case so separate from this. Taking the DRM point of view, it would be great to see:
|
Beta Was this translation helpful? Give feedback.
-
Based on what we already have in the current dashboard, my guess, looking comments above and thinking about the discussion I saw from kernel developers, is that the new dashboard could provide some features like:
|
Beta Was this translation helpful? Give feedback.
-
Small update on this topic, we've sent an RFP for UX Analysis and received some proposals. The LF project advisory board is now going through them to decide next steps. |
Beta Was this translation helpful? Give feedback.
-
@khilman started a thread on the mailing list a while ago: RFC: dashboards, visualization and analytics for test results. Having a GitHub discussion can also help gather such user stories and make it easier to engage with people not on the mailing list.
The aim is to have as many user-stories as possible to understand to which extent the KernelCI data may be used. Based on this initial research, we can then design a new dashboard and a set of tools to provide a better user experience.
Beta Was this translation helpful? Give feedback.
All reactions