Comment 77 for bug 793437

I have only more frustration for you: kernel #36 is untestable (same as #6, #11, #16, #21). Back when I was trying this myself, I recall reading "but git may eventually be unable to tell the first bad commit among a bad commit and one or more skipped commits" in the documentation. Perhaps that is why it seems to be making very poor choices of what commit to test next.

When I asked, long ago, about consequences for breaking the build, I meant that in any project I've worked on (all much smaller than this), if someone committed non-building code, that was the end of their privileges to do so without supervision. As many bad commits as there are in this project, I don't know what to think.