I understand that the goal is first to validate pending patches, than finding new bugs and showing the current state of net-next/net, but I think it might still be good to easily identify kernel crashes and warnings from the UI.
If I'm not mistaken, currently if a kernel panic is detected, the test will be marked as failed, like any issues we could have with the test. If it is possible to mark the tests that caused kernel oops and warnings, it might help identifying problematic patches quicker (and possibly bugs that were not introduced by the new patches). Could be fixed by introducing a new "critical" status?
I guess people having access to the server can easily grep in the logs to find crashes and warnings. I didn't find a way to list critical issues from the UI.
I understand that the goal is first to validate pending patches, than finding new bugs and showing the current state of net-next/net, but I think it might still be good to easily identify kernel crashes and warnings from the UI.
If I'm not mistaken, currently if a kernel panic is detected, the test will be marked as failed, like any issues we could have with the test. If it is possible to mark the tests that caused kernel oops and warnings, it might help identifying problematic patches quicker (and possibly bugs that were not introduced by the new patches). Could be fixed by introducing a new "critical" status?
I guess people having access to the server can easily
grepin the logs to find crashes and warnings. I didn't find a way to list critical issues from the UI.