{"thread":{"id":"42411","subject":"[PATCH v1 2/3] travis-ci: disable verbose test output","startedAt":"2016-05-22T11:00:53Z","lastAt":"2016-05-26T04:54:55Z","messageCount":10,"participants":["larsxschneider@gmail.com","Christian Couder","Lars Schneider","Pranit Bauva","Junio C Hamano","Jeff King"],"isPatch":true,"patchVersion":1,"patchTotal":3},"messages":[{"id":"287198","messageId":"1463914856-64745-1-git-send-email-larsxschneider@gmail.com","threadId":"42411","inReplyTo":null,"subject":"[PATCH v1 0/3] travis-ci: run Git bisect on failed tests","fromName":"","fromEmail":"larsxschneider@gmail.com","sentAt":"2016-05-22T11:00:53Z","receivedAt":"2016-05-22T11:00:53Z","isPatch":true,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"From: Lars Schneider <larsxschneider@gmail.com>\n\nThis patch series run Git bisect on failing tests on Travis CI.\n\nExample output on Travis CI:\nhttps://travis-ci.org/larsxschneider/git/jobs/132049871\n\nPlaintext example output:\nhttps://s3.amazonaws.com/archive.travis-ci.org/jobs/132049871/log.txt\n\nPlease scroll all the way down to see the bisect output.\n\nCheers,\nLars\n\n\nLars Schneider (3):\n  travis-ci: move \"after_failure\" code to dedicated file in /ci\n  travis-ci: disable verbose test output\n  travis-ci: run Git bisect on failed tests\n\n .travis.yml       | 14 ++--------\n ci/test-report.sh | 84 +++++++++++++++++++++++++++++++++++++++++++++++++++++++\n 2 files changed, 86 insertions(+), 12 deletions(-)\n create mode 100755 ci/test-report.sh\n\n--\n2.5.1\n"},{"id":"287199","messageId":"1463914856-64745-2-git-send-email-larsxschneider@gmail.com","threadId":"42411","inReplyTo":"1463914856-64745-1-git-send-email-larsxschneider@gmail.com","subject":"[PATCH v1 1/3] travis-ci: move \"after_failure\" code to dedicated file in /ci","fromName":"","fromEmail":"larsxschneider@gmail.com","sentAt":"2016-05-22T11:00:54Z","receivedAt":"2016-05-22T11:00:54Z","isPatch":true,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"From: Lars Schneider <larsxschneider@gmail.com>\n\nMove the code and adjust it to the Git shell script coding guidelines.\n\nSigned-off-by: Lars Schneider <larsxschneider@gmail.com>\n---\n .travis.yml       | 12 +-----------\n ci/test-report.sh | 19 +++++++++++++++++++\n 2 files changed, 20 insertions(+), 11 deletions(-)\n create mode 100755 ci/test-report.sh\n\ndiff --git a/.travis.yml b/.travis.yml\nindex adab5b8..a93ecb3 100644\n--- a/.travis.yml\n+++ b/.travis.yml\n@@ -101,17 +101,7 @@ script: make --quiet test\n after_failure:\n   - >\n     : '<-- Click here to see detailed test output!                                                        ';\n-    for TEST_EXIT in t/test-results/*.exit;\n-    do\n-      if [ \"$(cat \"$TEST_EXIT\")\" != \"0\" ];\n-      then\n-        TEST_OUT=\"${TEST_EXIT%exit}out\";\n-        echo \"------------------------------------------------------------------------\";\n-        echo \"$(tput setaf 1)${TEST_OUT}...$(tput sgr0)\";\n-        echo \"------------------------------------------------------------------------\";\n-        cat \"${TEST_OUT}\";\n-      fi;\n-    done;\n+    ./ci/test-report.sh\n \n notifications:\n   email: false\ndiff --git a/ci/test-report.sh b/ci/test-report.sh\nnew file mode 100755\nindex 0000000..d08a999\n--- /dev/null\n+++ b/ci/test-report.sh\n@@ -0,0 +1,19 @@\n+#!/bin/sh\n+#\n+# Print test results\n+#\n+for TEST_EXIT in t/test-results/*.exit\n+do\n+\tif test \"$(cat \"$TEST_EXIT\")\" != \"0\"\n+\tthen\n+\t\tTEST=\"${TEST_EXIT%.exit}\"\n+\t\tTEST_OUT=\"${TEST}.out\"\n+\t\techo \"------------------------------------------------------------------------\"\n+\t\techo \"  $(tput setaf 1)${TEST} Output$(tput sgr0)\"\n+\t\techo \"------------------------------------------------------------------------\"\n+\t\tcat \"$TEST_OUT\"\n+\t\techo \"\"\n+\t\techo \"\"\n+\tfi\n+done\n+\n-- \n2.5.1\n"},{"id":"287197","messageId":"1463914856-64745-3-git-send-email-larsxschneider@gmail.com","threadId":"42411","inReplyTo":"1463914856-64745-1-git-send-email-larsxschneider@gmail.com","subject":"[PATCH v1 2/3] travis-ci: disable verbose test output","fromName":"","fromEmail":"larsxschneider@gmail.com","sentAt":"2016-05-22T11:00:55Z","receivedAt":"2016-05-22T11:00:55Z","isPatch":true,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"From: Lars Schneider <larsxschneider@gmail.com>\n\nThe verbose output clutters the Travis CI webview and is not really\nuseful since test debugging usually happens on a local machine.\n\nSigned-off-by: Lars Schneider <larsxschneider@gmail.com>\n---\n .travis.yml | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/.travis.yml b/.travis.yml\nindex a93ecb3..81d2027 100644\n--- a/.travis.yml\n+++ b/.travis.yml\n@@ -29,7 +29,7 @@ env:\n     - LINUX_GIT_LFS_VERSION=\"1.2.0\"\n     - DEFAULT_TEST_TARGET=prove\n     - GIT_PROVE_OPTS=\"--timer --jobs 3 --state=failed,slow,save\"\n-    - GIT_TEST_OPTS=\"--verbose --tee\"\n+    - GIT_TEST_OPTS=\"--tee\"\n     - GIT_TEST_CLONE_2GB=YesPlease\n     # t9810 occasionally fails on Travis CI OS X\n     # t9816 occasionally fails with \"TAP out of sequence errors\" on Travis CI OS X\n-- \n2.5.1\n"},{"id":"287200","messageId":"1463914856-64745-4-git-send-email-larsxschneider@gmail.com","threadId":"42411","inReplyTo":"1463914856-64745-1-git-send-email-larsxschneider@gmail.com","subject":"[PATCH v1 3/3] travis-ci: run Git bisect on failed tests","fromName":"","fromEmail":"larsxschneider@gmail.com","sentAt":"2016-05-22T11:00:56Z","receivedAt":"2016-05-22T11:00:56Z","isPatch":true,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"From: Lars Schneider <larsxschneider@gmail.com>\n\nJunio usually pushes many commits at once to the public \"pu\"/\"next\"/\n\"master\" branches. If a test fails then it is not obvious what commit\ncaused the failure. Therefore we run Git bisect with the merge base\nbetween the failing rev and its more stable branch (\"next\" for \"pu\",\n\"master\" for \"next\", and \"maint\" for \"master\") as good ref to find the\noffending commit. This is only enabled on \"github.com/git/git\" because\nthere we can assume that all relevant branches are up to date.\n\nSigned-off-by: Lars Schneider <larsxschneider@gmail.com>\n---\n .travis.yml       |  2 +-\n ci/test-report.sh | 65 +++++++++++++++++++++++++++++++++++++++++++++++++++++++\n 2 files changed, 66 insertions(+), 1 deletion(-)\n\ndiff --git a/.travis.yml b/.travis.yml\nindex 81d2027..922807b 100644\n--- a/.travis.yml\n+++ b/.travis.yml\n@@ -101,7 +101,7 @@ script: make --quiet test\n after_failure:\n   - >\n     : '<-- Click here to see detailed test output!                                                        ';\n-    ./ci/test-report.sh\n+    ./ci/test-report.sh $TRAVIS_REPO_SLUG $TRAVIS_BRANCH;\n \n notifications:\n   email: false\ndiff --git a/ci/test-report.sh b/ci/test-report.sh\nindex d08a999..8f7adad 100755\n--- a/ci/test-report.sh\n+++ b/ci/test-report.sh\n@@ -1,5 +1,12 @@\n #!/bin/sh\n #\n+# Print test results and run Git bisect on failed tests.\n+#\n+REPO_ORG_NAME=$1\n+CURRENT_BRANCH_NAME=$2\n+\n+\n+#\n # Print test results\n #\n for TEST_EXIT in t/test-results/*.exit\n@@ -17,3 +24,61 @@ do\n \tfi\n done\n \n+\n+#\n+# Run Git bisect\n+#\n+run_bisect () {\n+\tTEST_SCRIPT=$1\n+\tBAD_REV=$2\n+\tGOOD_RV=$3\n+\tTMPDIR=$(mktemp -d -t \"ci-report-bisect-XXXXXX\" 2>/dev/null)\n+\tcat > \"$TMPDIR/bisect-run.sh\" <<EOF\n+\n+EOF\n+\tchmod +x \"$TMPDIR/bisect-run.sh\"\n+\tgit bisect start $BAD_REV $GOOD_RV\n+\tgit bisect run \"$TMPDIR/bisect-run.sh\"\n+\tif test -e ./t/$TEST_SCRIPT.sh && make --jobs=2 >/dev/null 2>&1\n+\tthen\n+\t\tcd t && ./$TEST_SCRIPT.sh >/dev/null 2>&1\n+\telse\n+\t\t# If the test file does not exist or the build fails then tell\n+\t\t# Git bisect to skip the commit.\n+\t\texit 125\n+\tfi\n+\tgit bisect reset >/dev/null 2>&1\n+}\n+\n+case \"$CURRENT_BRANCH_NAME\" in\n+\tmaster) STABLE_BRANCH=\"maint\";;\n+\tnext)   STABLE_BRANCH=\"master\";;\n+\tpu)     STABLE_BRANCH=\"next\";;\n+esac\n+\n+if test \"$REPO_ORG_NAME\" = \"git/git\" && test -n $STABLE_BRANCH\n+then\n+\tBAD_REV=$(git rev-parse HEAD)\n+\n+\t# Travis CI clones are shallow. It is possible that the last good revision\n+\t# was not fetched, yet. Therefore we need to fetch all commits on the\n+\t# stable branch.\n+\tgit config remote.origin.fetch \"+refs/heads/$STABLE_BRANCH:refs/remotes/origin/$STABLE_BRANCH\"\n+\tgit fetch --unshallow --quiet\n+\tLAST_GOOD_REV=$(git merge-base $BAD_REV \"remotes/origin/$STABLE_BRANCH\")\n+\n+\tfor TEST_EXIT in t/test-results/*.exit\n+\tdo\n+\t\tif test \"$(cat \"$TEST_EXIT\")\" != \"0\"\n+\t\tthen\n+\t\t\tTEST=\"${TEST_EXIT%.exit}\"\n+\t\t\tTEST_SCRIPT=${TEST#t/test-results/}\n+\t\t\techo \"------------------------------------------------------------------------\"\n+\t\t\techo \"  $(tput setaf 1)${TEST} Bisect$(tput sgr0)\"\n+\t\t\techo \"------------------------------------------------------------------------\"\n+\t\t\trun_bisect $TEST_SCRIPT $BAD_REV $LAST_GOOD_REV\n+\t\t\techo \"\"\n+\t\t\techo \"\"\n+\t\tfi\n+\tdone\n+fi\n-- \n2.5.1\n"},{"id":"287206","messageId":"CAP8UFD3TJ7mJEu2xCXhrspHY1v02uTonUGdszZbcQGf9ne9_Cg@mail.gmail.com","threadId":"42411","inReplyTo":"1463914856-64745-4-git-send-email-larsxschneider@gmail.com","subject":"Re: [PATCH v1 3/3] travis-ci: run Git bisect on failed tests","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2016-05-22T15:35:52Z","receivedAt":"2016-05-22T15:35:52Z","isPatch":true,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Sun, May 22, 2016 at 1:00 PM,  <larsxschneider@gmail.com> wrote:\n\n[...]\n\n> +#\n> +# Run Git bisect\n> +#\n> +run_bisect () {\n> +       TEST_SCRIPT=$1\n> +       BAD_REV=$2\n> +       GOOD_RV=$3\n> +       TMPDIR=$(mktemp -d -t \"ci-report-bisect-XXXXXX\" 2>/dev/null)\n> +       cat > \"$TMPDIR/bisect-run.sh\" <<EOF\n> +\n> +EOF\n> +       chmod +x \"$TMPDIR/bisect-run.sh\"\n> +       git bisect start $BAD_REV $GOOD_RV\n> +       git bisect run \"$TMPDIR/bisect-run.sh\"\n> +       if test -e ./t/$TEST_SCRIPT.sh && make --jobs=2 >/dev/null 2>&1\n> +       then\n> +               cd t && ./$TEST_SCRIPT.sh >/dev/null 2>&1\n> +       else\n> +               # If the test file does not exist or the build fails then tell\n> +               # Git bisect to skip the commit.\n> +               exit 125\n> +       fi\n\nShouldn't all the above \"if ... fi\" be in the here document creating\n\"$TMPDIR/bisect-run.sh\"?\n\n> +       git bisect reset >/dev/null 2>&1\n> +}\n"},{"id":"287207","messageId":"DEFC086F-6206-4598-8355-0394C6070F59@gmail.com","threadId":"42411","inReplyTo":"CAP8UFD3TJ7mJEu2xCXhrspHY1v02uTonUGdszZbcQGf9ne9_Cg@mail.gmail.com","subject":"Re: [PATCH v1 3/3] travis-ci: run Git bisect on failed tests","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2016-05-22T16:35:37Z","receivedAt":"2016-05-22T16:35:37Z","isPatch":true,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\n> On 22 May 2016, at 17:35, Christian Couder <christian.couder@gmail.com> wrote:\n> \n> On Sun, May 22, 2016 at 1:00 PM,  <larsxschneider@gmail.com> wrote:\n> \n> [...]\n> \n>> +#\n>> +# Run Git bisect\n>> +#\n>> +run_bisect () {\n>> +       TEST_SCRIPT=$1\n>> +       BAD_REV=$2\n>> +       GOOD_RV=$3\n>> +       TMPDIR=$(mktemp -d -t \"ci-report-bisect-XXXXXX\" 2>/dev/null)\n>> +       cat > \"$TMPDIR/bisect-run.sh\" <<EOF\n>> +\n>> +EOF\n>> +       chmod +x \"$TMPDIR/bisect-run.sh\"\n>> +       git bisect start $BAD_REV $GOOD_RV\n>> +       git bisect run \"$TMPDIR/bisect-run.sh\"\n>> +       if test -e ./t/$TEST_SCRIPT.sh && make --jobs=2 >/dev/null 2>&1\n>> +       then\n>> +               cd t && ./$TEST_SCRIPT.sh >/dev/null 2>&1\n>> +       else\n>> +               # If the test file does not exist or the build fails then tell\n>> +               # Git bisect to skip the commit.\n>> +               exit 125\n>> +       fi\n> \n> Shouldn't all the above \"if ... fi\" be in the here document creating\n> \"$TMPDIR/bisect-run.sh\"?\nOhh. Absolutely... I wonder what happened. I'll post a v2.\n\nThank you,\nLars\n\n\n> \n>> +       git bisect reset >/dev/null 2>&1\n>> +}\n"},{"id":"287208","messageId":"CAFZEwPOuCRJFx0wH5YHKxWNmjkvi2R6s5G0Bw+WrnHywT3cR0g@mail.gmail.com","threadId":"42411","inReplyTo":"1463914856-64745-4-git-send-email-larsxschneider@gmail.com","subject":"Re: [PATCH v1 3/3] travis-ci: run Git bisect on failed tests","fromName":"Pranit Bauva","fromEmail":"pranit.bauva@gmail.com","sentAt":"2016-05-22T17:21:20Z","receivedAt":"2016-05-22T17:21:20Z","isPatch":true,"sender":{"key":"pranit.bauva@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2959938?v=4"},"body":"Hey Lars,\n\nOn Sun, May 22, 2016 at 4:30 PM,  <larsxschneider@gmail.com> wrote:\n> From: Lars Schneider <larsxschneider@gmail.com>\n>\n> Junio usually pushes many commits at once to the public \"pu\"/\"next\"/\n> \"master\" branches. If a test fails then it is not obvious what commit\n> caused the failure. Therefore we run Git bisect with the merge base\n> between the failing rev and its more stable branch (\"next\" for \"pu\",\n> \"master\" for \"next\", and \"maint\" for \"master\") as good ref to find the\n> offending commit. This is only enabled on \"github.com/git/git\" because\n> there we can assume that all relevant branches are up to date.\n>\n> Signed-off-by: Lars Schneider <larsxschneider@gmail.com>\n> ---\n>  .travis.yml       |  2 +-\n>  ci/test-report.sh | 65 +++++++++++++++++++++++++++++++++++++++++++++++++++++++\n>  2 files changed, 66 insertions(+), 1 deletion(-)\n>\n> diff --git a/.travis.yml b/.travis.yml\n> index 81d2027..922807b 100644\n> --- a/.travis.yml\n> +++ b/.travis.yml\n> @@ -101,7 +101,7 @@ script: make --quiet test\n>  after_failure:\n>    - >\n>      : '<-- Click here to see detailed test output!                                                        ';\n> -    ./ci/test-report.sh\n> +    ./ci/test-report.sh $TRAVIS_REPO_SLUG $TRAVIS_BRANCH;\n>\n>  notifications:\n>    email: false\n> diff --git a/ci/test-report.sh b/ci/test-report.sh\n> index d08a999..8f7adad 100755\n> --- a/ci/test-report.sh\n> +++ b/ci/test-report.sh\n> @@ -1,5 +1,12 @@\n>  #!/bin/sh\n>  #\n> +# Print test results and run Git bisect on failed tests.\n> +#\n> +REPO_ORG_NAME=$1\n> +CURRENT_BRANCH_NAME=$2\n> +\n> +\n> +#\n>  # Print test results\n>  #\n>  for TEST_EXIT in t/test-results/*.exit\n> @@ -17,3 +24,61 @@ do\n>         fi\n>  done\n>\n> +\n> +#\n> +# Run Git bisect\n> +#\n> +run_bisect () {\n> +       TEST_SCRIPT=$1\n> +       BAD_REV=$2\n> +       GOOD_RV=$3\n> +       TMPDIR=$(mktemp -d -t \"ci-report-bisect-XXXXXX\" 2>/dev/null)\n> +       cat > \"$TMPDIR/bisect-run.sh\" <<EOF\n\nIf you are doing a re-roll, then you could probably fix the style issue.\n' cat >\"$TMPDIR...\"  '\n\n> +\n> +EOF\n> +       chmod +x \"$TMPDIR/bisect-run.sh\"\n> +       git bisect start $BAD_REV $GOOD_RV\n> +       git bisect run \"$TMPDIR/bisect-run.sh\"\n> +       if test -e ./t/$TEST_SCRIPT.sh && make --jobs=2 >/dev/null 2>&1\n> +       then\n> +               cd t && ./$TEST_SCRIPT.sh >/dev/null 2>&1\n> +       else\n> +               # If the test file does not exist or the build fails then tell\n> +               # Git bisect to skip the commit.\n> +               exit 125\n> +       fi\n> +       git bisect reset >/dev/null 2>&1\n> +}\n> +\n> +case \"$CURRENT_BRANCH_NAME\" in\n> +       master) STABLE_BRANCH=\"maint\";;\n> +       next)   STABLE_BRANCH=\"master\";;\n> +       pu)     STABLE_BRANCH=\"next\";;\n> +esac\n> +\n> +if test \"$REPO_ORG_NAME\" = \"git/git\" && test -n $STABLE_BRANCH\n> +then\n> +       BAD_REV=$(git rev-parse HEAD)\n> +\n> +       # Travis CI clones are shallow. It is possible that the last good revision\n> +       # was not fetched, yet. Therefore we need to fetch all commits on the\n> +       # stable branch.\n> +       git config remote.origin.fetch \"+refs/heads/$STABLE_BRANCH:refs/remotes/origin/$STABLE_BRANCH\"\n> +       git fetch --unshallow --quiet\n> +       LAST_GOOD_REV=$(git merge-base $BAD_REV \"remotes/origin/$STABLE_BRANCH\")\n> +\n> +       for TEST_EXIT in t/test-results/*.exit\n> +       do\n> +               if test \"$(cat \"$TEST_EXIT\")\" != \"0\"\n> +               then\n> +                       TEST=\"${TEST_EXIT%.exit}\"\n> +                       TEST_SCRIPT=${TEST#t/test-results/}\n> +                       echo \"------------------------------------------------------------------------\"\n> +                       echo \"  $(tput setaf 1)${TEST} Bisect$(tput sgr0)\"\n> +                       echo \"------------------------------------------------------------------------\"\n> +                       run_bisect $TEST_SCRIPT $BAD_REV $LAST_GOOD_REV\n> +                       echo \"\"\n> +                       echo \"\"\n> +               fi\n> +       done\n> +fi\n\nRegards,\nPranit Bauva\n"},{"id":"287220","messageId":"xmqq1t4tbmbp.fsf@gitster.mtv.corp.google.com","threadId":"42411","inReplyTo":"1463914856-64745-4-git-send-email-larsxschneider@gmail.com","subject":"Re: [PATCH v1 3/3] travis-ci: run Git bisect on failed tests","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-05-23T01:22:02Z","receivedAt":"2016-05-23T01:22:02Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"larsxschneider@gmail.com writes:\n\n> Junio usually pushes many commits at once to the public \"pu\"/\"next\"/\n> \"master\" branches. If a test fails then it is not obvious what commit\n> caused the failure. Therefore we run Git bisect with the merge base\n> between the failing rev and its more stable branch (\"next\" for \"pu\",\n> \"master\" for \"next\", and \"maint\" for \"master\") as good ref to find the\n> offending commit. This is only enabled on \"github.com/git/git\" because\n> there we can assume that all relevant branches are up to date.\n\nJust FYI, 'git log next..pu' is not a very interesting range unless\nyou also use the \"--no-merges\" option.\n\nIs there a good way to tell the CI that, instead of testing 'pu' (or\na specific branch in general), test all new commits that appear on\nthe first-parent chain between 'master'..'pu'?\n\nIt would be ideal if CI can do this every time 'master' and 'pu'\ngets updated.\n\n - Find all commits that appear on the first-parent chain between\n   'master..pu'.\n\n - For each of them:\n\n   - Test it.  This tests the merge result and can catch breakages\n     introduced by mismerging.\n\n   - Also test its second parent if it is a merge.  This tests the\n     tip of each topic branch in isolation.  CI gets a bonus point\n     if it can remember that the tip of the topic did not move and\n     the commit already passed the test to skip it ;-)\n\n - Optionally, for those topics that failed the \"tip of the topic\n   branch\" test, \"bisect master..$topic\" to see where it breaks.\n\nThe thing is, \"bisect\" works only when you have a _single_ cause of\nbreakage, but because 'pu' is a pile of unsorted raw material yet to\nbe sifted into dirt and gem, once you see a failure at the tip of\n'pu', mechanical 'bisect run' may not be a very useful tool, as you\ndo not know if there is only one breakage you are looking for.\n\nBecause the unit of integration we use is a topic branch (not an\nindividual commit on a topic branch), \"this topic is broken\", and\n\"this topic itself may be good, but merging it breaks 'pu'\" are far\nmore interesting and relevant piece of information than \"this commit\nis what broke 'pu'\".\n"},{"id":"287233","messageId":"BCC937A6-27E4-4849-80C7-82EC155F08C1@gmail.com","threadId":"42411","inReplyTo":"CAFZEwPOuCRJFx0wH5YHKxWNmjkvi2R6s5G0Bw+WrnHywT3cR0g@mail.gmail.com","subject":"Re: [PATCH v1 3/3] travis-ci: run Git bisect on failed tests","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2016-05-23T08:36:19Z","receivedAt":"2016-05-23T08:36:19Z","isPatch":true,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"\n> On 22 May 2016, at 19:21, Pranit Bauva <pranit.bauva@gmail.com> wrote:\n> \n> Hey Lars,\n> \n> On Sun, May 22, 2016 at 4:30 PM,  <larsxschneider@gmail.com> wrote:\n>> From: Lars Schneider <larsxschneider@gmail.com>\n>> \n...\n>> +\n>> +#\n>> +# Run Git bisect\n>> +#\n>> +run_bisect () {\n>> +       TEST_SCRIPT=$1\n>> +       BAD_REV=$2\n>> +       GOOD_RV=$3\n>> +       TMPDIR=$(mktemp -d -t \"ci-report-bisect-XXXXXX\" 2>/dev/null)\n>> +       cat > \"$TMPDIR/bisect-run.sh\" <<EOF\n> \n> If you are doing a re-roll, then you could probably fix the style issue.\n> ' cat >\"$TMPDIR...\"  '\n\nGood eye :-) I will fix this, too.\n\nThank you,\nLars\n"},{"id":"287552","messageId":"20160526045455.GD6756@sigill.intra.peff.net","threadId":"42411","inReplyTo":"1463914856-64745-3-git-send-email-larsxschneider@gmail.com","subject":"Re: [PATCH v1 2/3] travis-ci: disable verbose test output","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2016-05-26T04:54:55Z","receivedAt":"2016-05-26T04:54:55Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sun, May 22, 2016 at 01:00:55PM +0200, larsxschneider@gmail.com wrote:\n\n> From: Lars Schneider <larsxschneider@gmail.com>\n> \n> The verbose output clutters the Travis CI webview and is not really\n> useful since test debugging usually happens on a local machine.\n\nI have not really been using the Travis CI results, so perhaps my\nopinion does not count. But in other systems, I have found that the more\nverbose the CI output, the better, simply because you will inevitably be\nfaced with a test that breaks on CI and not your local machine, and you\nwill have no way to get more details.\n\nI don't know if Travis provides a better way to hide the output in the\nnon-failing cases.\n\n-Peff\n"}]}