[SPIKE] Bisection
Suggested by GregKH who wants to know the exact commit which introduced the failure.
Some quick questions and notes that come to mind:
- The kernel needs to run on the same HW setup (ideally same machine) - if the failure occurred because of a bug in a specific driver running on a different machine which doesn't have it won't help diagnose it.
- Resource utilization. Can we keep the machine reserved and submit new recipes (with new kernels and failed test(s)) to it? Should be easier to do with split provisioning and test running.
- What to do with hard to reproduce bugs? A message that states we weren't able to reproduce the failure so either the top commit is the problem or it's a deeply hidden bug?
- What to do with patch CI? The bug is either introduced by patches OR is a hard-to-reproduce and was there previously. In the first case, we don't even need bisection. In the second it won't help us with debugging.
JIRA ticket created by @veruu
Edited by Veronika Kabátová