Is there a #CLI tool that helps binary-search/bisect towards finding the cause of a problem, but *outside* git?
For example: I've got a data file that's successfully processed by v1 of a command, but v200 fails. I can hack my way towards a script that tries out v100, and use that result to manually choose to test with v50/v150, and so on.
But is there tooling out there that can help wrap up that binary-search workflow? #SysAdmin #DevOps #SRE #DataScience #BinarySearch #Bisect
@jonathanmatthews Are the different versions of the script stored in some form of VCS? I know you said "outside git" but this seems tailor-made for git-bisect...
@mjturner The "script" I mentioned isn't the problem - it's just something I tentatively thought up as an interface to the underlying issue.
The actual problem is "these website source files produce the right output when Hugo v$OLD builds the site, but Hugo v$LATEST emits the "wrong" output. Given that I have a test for wrong vs "right", and a list of the many Hugo versions whose release notes might mention the cause of the problem, how can I identify the relevant version?"
