So committing at 8h00 at -0700 punches the same slot as 08h00 at +0200.
Remember the test states on rebases.
This should work for anything that is append-only, but I'm using it to experiment with couch and be able to undo my changes.
Before, when you ran the command in in bare repo or a non-repo, lots of errors printed. Now, it just explains what's wrong once and bails out.
… option and all commits already passed.
…e than x seconds.
… only the latest commit and if it fails, then run git-test-bisect automatically to find the first bad commit.
…eful on the build server so the log output represents one success or failure. Then it builds again to advance in the sequence.
… out to never be useful chiefly because it so failure maybe due to system resources, locked files, or other issues which are not a reflection on the source code commit.
…eeping files listed in .gitexcept.
…ause if you need to interrupt test-sequence then the temp branch gets left around. So instead, test-sequence simply checks out the hash to achieve the same purpose.
…revision as whether it already has a pass or fail ref to avoid retesting any revision alredy tested. It will report already passed <revision>, already failed <revision> and stop, or run a new test and record the results.