Hey Ewoud, +1 for bisect,
what's up Ewoud?, this email reminds me good old rhevm-api days. On 01/29/2013 05:36 PM, Ewoud Kohl van Wijngaarden wrote: > May I recommend git bisect? See http://lwn.net/Articles/317154/ or > http://clock.co.uk/tech-blogs/git-bisect-simple-examples-and-automation > as well. > > First you find a known BAD, for example master. Then you find a known > GOOD (for example 100 commits ago in master: master~100). Then we can > use a script to determine if it's good. I'm assuming mvn test will be > sufficient, but maybe you can refine this to only test for a specific > unit test. > > git bisect start BAD GOOD > git bisect run mvn test > > Now it will do a binary search in your history trying to find the commit > that broke mvn test. -- Michael Pasternak RedHat, ENG-Virtualization R&D _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
