Hi Lars & Junio, On Fri, 22 Apr 2016, Junio C Hamano wrote: > Lars Schneider <larsxschneider@xxxxxxxxx> writes: > > > Thanks for the explanation. My intention was not to be offensive. > > I was curious about your workflow and I was wondering if the > > Travis CI integration could be useful for you in any way. > > Don't worry; I didn't feel offended. The Travis stuff running on > the branches at http://github.com/git/git would surely catch issues > on MacOSX and/or around git-p4 (neither of which I test myself when > merging to 'pu') before they hit 'next', and that is already helping > us greatly. I agree that it helps to catch those Mac and P4 issues early. However, it is possible that bogus errors are reported that might not have been introduced by the changes of the PR, and I find it relatively hard to figure out the specifics. Take for example https://travis-ci.org/git/git/jobs/124767554 It appears that t9824 fails with my interactive rebase work on MacOSX, both Clang and GCC versions. I currently have no access to a Mac for developing (so I am denied my favorite debugging technique: sh t... -i -v -x), and I seem to be unable to find any useful log of what went wrong *specifically*. Any ideas how to find out? Ciao, Dscho -- 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