From: Christian Couder <christian.couder@gmail.com>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH v1 3/3] travis-ci: run Git bisect on failed tests
Date: Sun, 22 May 2016 17:35:52 +0200 [thread overview]
Message-ID: <CAP8UFD3TJ7mJEu2xCXhrspHY1v02uTonUGdszZbcQGf9ne9_Cg@mail.gmail.com> (raw)
In-Reply-To: <1463914856-64745-4-git-send-email-larsxschneider@gmail.com>
On Sun, May 22, 2016 at 1:00 PM, <larsxschneider@gmail.com> wrote:
[...]
> +#
> +# Run Git bisect
> +#
> +run_bisect () {
> + TEST_SCRIPT=$1
> + BAD_REV=$2
> + GOOD_RV=$3
> + TMPDIR=$(mktemp -d -t "ci-report-bisect-XXXXXX" 2>/dev/null)
> + cat > "$TMPDIR/bisect-run.sh" <<EOF
> +
> +EOF
> + chmod +x "$TMPDIR/bisect-run.sh"
> + git bisect start $BAD_REV $GOOD_RV
> + git bisect run "$TMPDIR/bisect-run.sh"
> + if test -e ./t/$TEST_SCRIPT.sh && make --jobs=2 >/dev/null 2>&1
> + then
> + cd t && ./$TEST_SCRIPT.sh >/dev/null 2>&1
> + else
> + # If the test file does not exist or the build fails then tell
> + # Git bisect to skip the commit.
> + exit 125
> + fi
Shouldn't all the above "if ... fi" be in the here document creating
"$TMPDIR/bisect-run.sh"?
> + git bisect reset >/dev/null 2>&1
> +}
next prev parent reply other threads:[~2016-05-22 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-22 11:00 [PATCH v1 0/3] travis-ci: run Git bisect on failed tests larsxschneider
2016-05-22 11:00 ` [PATCH v1 1/3] travis-ci: move "after_failure" code to dedicated file in /ci larsxschneider
2016-05-22 11:00 ` [PATCH v1 2/3] travis-ci: disable verbose test output larsxschneider
2016-05-26 4:54 ` Jeff King
2016-05-22 11:00 ` [PATCH v1 3/3] travis-ci: run Git bisect on failed tests larsxschneider
2016-05-22 15:35 ` Christian Couder [this message]
2016-05-22 16:35 ` Lars Schneider
2016-05-22 17:21 ` Pranit Bauva
2016-05-23 8:36 ` Lars Schneider
2016-05-23 1:22 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP8UFD3TJ7mJEu2xCXhrspHY1v02uTonUGdszZbcQGf9ne9_Cg@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).