Re: git bisect code 125 - "WFT?"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jeff King <peff@xxxxxxxx> writes:

>   2. If we do detect such a mishap, I'm not sure that "indeterminate
>      result" is necessarily the best result, as that will just keep
>      trying more and more commits without success. It is more likely a
>      sign of a poorly written test script, and the best thing we could
>      do is die and say "your test script looks buggy".

Exactly. I agree "Aborting the bisect as run-script is a crap" is the
right thing to do here.

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]