4 ms·
I think you misunderstood. The test is brand new. As in, you find a problem that nobody has identified before and want to see how/when it was introduced. Eas
by taeric 12y ago
I think you misunderstood. The test is brand new. As in, you find a problem that nobody has identified before and want to see how/when it was introduced.
Easy way to do this is put your test external to the tree. Then, bisect as normal for git, and run your test.
This is probably not uncommon for kernel tests, as you often have a test which could be "does this random laptop resume from sleep correctly?" Not really easy to automate that. And doesn't live in your tree.
- Hello71 12y ago> "does this random laptop resume from sleep correctly?" Not really easy to automate that. that's what rtcwake is for
- deleted 12y ago[deleted]
- taeric 12y agoRight, my point was more that often everything will be working great for the main developer's laptop. I did not think it was uncommon to have someone come out of the weeds with a specific laptop that doesn't work. Or worse, it works if you sleep using the "sleep" button, but not if you close the lid. So, yes, you may be able to automate it later, once you fully understand the specifics that cause it to not rewake. Possibly specific to how it went to sleep with the lid close. Until then, it is nice to be able to do ad hoc tests when necessary.