Re: [PATCH v1 3/3] travis-ci: run Git bisect on failed tests

2016-05-23 Thread Lars Schneider
> On 22 May 2016, at 19:21, Pranit Bauva wrote: > > Hey Lars, > > On Sun, May 22, 2016 at 4:30 PM, wrote: >> From: Lars Schneider >> ... >> + >> +# >> +# Run Git bisect >> +# >> +run_bisect () { >> + TEST_SCRIPT=$1 >> + BAD_REV=$2 >> + GOOD_RV=$3 >> + TMPDIR=$(mktemp

Re: [PATCH v1 3/3] travis-ci: run Git bisect on failed tests

2016-05-22 Thread Junio C Hamano
larsxschnei...@gmail.com writes: > Junio usually pushes many commits at once to the public "pu"/"next"/ > "master" branches. If a test fails then it is not obvious what commit > caused the failure. Therefore we run Git bisect with the merge base > between the failing rev and its more stable branch

Re: [PATCH v1 3/3] travis-ci: run Git bisect on failed tests

2016-05-22 Thread Pranit Bauva
Hey Lars, On Sun, May 22, 2016 at 4:30 PM, wrote: > From: Lars Schneider > > Junio usually pushes many commits at once to the public "pu"/"next"/ > "master" branches. If a test fails then it is not obvious what commit > caused the failure. Therefore we run Git bisect with the merge base > betwe

Re: [PATCH v1 3/3] travis-ci: run Git bisect on failed tests

2016-05-22 Thread Lars Schneider
> On 22 May 2016, at 17:35, Christian Couder wrote: > > On Sun, May 22, 2016 at 1:00 PM, wrote: > > [...] > >> +# >> +# Run Git bisect >> +# >> +run_bisect () { >> + TEST_SCRIPT=$1 >> + BAD_REV=$2 >> + GOOD_RV=$3 >> + TMPDIR=$(mktemp -d -t "ci-report-bisect-XX" 2>

Re: [PATCH v1 3/3] travis-ci: run Git bisect on failed tests

2016-05-22 Thread Christian Couder
On Sun, May 22, 2016 at 1:00 PM, wrote: [...] > +# > +# Run Git bisect > +# > +run_bisect () { > + TEST_SCRIPT=$1 > + BAD_REV=$2 > + GOOD_RV=$3 > + TMPDIR=$(mktemp -d -t "ci-report-bisect-XX" 2>/dev/null) > + cat > "$TMPDIR/bisect-run.sh" < + > +EOF > + c

[PATCH v1 3/3] travis-ci: run Git bisect on failed tests

2016-05-22 Thread larsxschneider
From: Lars Schneider Junio usually pushes many commits at once to the public "pu"/"next"/ "master" branches. If a test fails then it is not obvious what commit caused the failure. Therefore we run Git bisect with the merge base between the failing rev and its more stable branch ("next" for "pu",