From: larsxschneider@gmail.com
To: git@vger.kernel.org
Cc: sunshine@sunshineco.com, sschuberth@gmail.com,
Matthieu.Moy@grenoble-inp.fr, avila.jn@gmail.com,
luke@diamand.org, dturner@twopensource.com,
Lars Schneider <larsxschneider@gmail.com>
Subject: [PATCH v4 0/4] Add Travis CI support
Date: Fri, 6 Nov 2015 09:58:39 +0100 [thread overview]
Message-ID: <1446800323-2914-1-git-send-email-larsxschneider@gmail.com> (raw)
From: Lars Schneider <larsxschneider@gmail.com>
diff to v3:
* Removed git-p4 OS X test fixes and submitted them in a separate roll as
request by Junio [1].
* Fix brew formula typo.
(thanks Eric)
* Move "make configure && ./configure" from "install" to "before_script" phase.
(thanks Sebastian)
* Run a build configuration with all kinds of "NO_*" flags. I don't understand
all of them. Please let me know if some of them don't make sense. I also
noticed that "NO_ICONV" will cause various tests to fail [2]. Is this a bug
that should be fixed as part of this roll? If this is no bug, would it make
sense to remove this flag?
(thanks Junio, Matthieu)
* Run make with multiple jobs. I found that -j2 is the fastest for building
git on Travis. -j6 is the fastest to run the unit tests. I limited that to
-j3 because I had the impression that I got more test failures with higher
utilization.
(thanks Jean-Noel, Matthieu)
* Run Linux builds on new Travis CI container infrastructure .
(thanks Matthieu)
* Print Perforce/Git-LFS binary versions
* Run tests with test extension flags enabled. Unfortunately "GIT_TEST_LONG"
caused "t0021" to fail on Linux [3]. I wasn't able to reproduce this on my
local machine, yet. Ideas anyone? Furthermore "GETTEXT_POISON" causes a bunch
of failed tests on Linux and OS X [4]. Is this intentional or a bug?
* Print verbose output of failed tests in the "after_failure" phase. Please
note the little triangle on the left in the TravisCI log to expand the failed
test output.
* Update LFS to 1.0.2
* Accept SIGPIPE output in some tests (similar to [5] by Junio)
* Make git-p4 tests more robust with a general timeout and retry logic for
cleanup commands (I now the "rm" and "mkdir" retry looks stupid but I was
able to reproduce this error on TravisCI consistently - does anyone have
a possible explanation why this could be necessary? Open file handles?)
* Disable email notifications (at least initially). I found and fixed a few
issues that caused flaky tests. However, I expect there are more and we can
only find them over time. If you add this patch then TravisCI can run
silently in the background. If people want to look at the TravisCI result
then they can. All other people are not bothered by emails. If we find in
six months from now that TravisCI has too many false failures then we could
remove the .travis.yml, again, and move on.
I had to apply this patch on master to get David Turner's fix for flaky
t7063 [6]/[7].
You can find the TravisCI run for this roll here:
https://travis-ci.org/larsxschneider/git/builds/89598194
Cheers,
Lars
[1] http://thread.gmane.org/gmane.comp.version-control.git/279348/focus=279362
[2] https://travis-ci.org/larsxschneider/git/builds/89555114
[3] https://travis-ci.org/larsxschneider/git/builds/89554983
[4] https://travis-ci.org/larsxschneider/git/builds/89554899
[5] http://thread.gmane.org/gmane.comp.version-control.git/280120/focus=280543
[6] http://thread.gmane.org/gmane.comp.version-control.git/279647
[7] http://thread.gmane.org/gmane.comp.version-control.git/279889
Lars Schneider (4):
add function test_must_fail_or_sigpipe and use it to fix flaky tests
git-p4: add p4d timeout in tests
git-p4: retry kill/cleanup operations in tests with timeout
Add Travis CI support
.travis.yml | 131 ++++++++++++++++++++++++++++++++++++++++
t/lib-git-p4.sh | 51 +++++++++++++---
t/t5504-fetch-receive-strict.sh | 3 +-
t/t5516-fetch-push.sh | 8 +--
t/test-lib-functions.sh | 23 +++++++
5 files changed, 201 insertions(+), 15 deletions(-)
create mode 100644 .travis.yml
--
2.5.1
next reply other threads:[~2015-11-06 8:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 8:58 larsxschneider [this message]
2015-11-06 8:58 ` [PATCH v4 1/4] add function test_must_fail_or_sigpipe and use it to fix flaky tests larsxschneider
2015-11-06 18:27 ` Junio C Hamano
2015-11-06 18:49 ` Junio C Hamano
2015-11-06 8:58 ` [PATCH v4 2/4] git-p4: add p4d timeout in tests larsxschneider
2015-11-06 9:23 ` Eric Sunshine
2015-11-06 13:20 ` Lars Schneider
2015-11-06 8:58 ` [PATCH v4 3/4] git-p4: retry kill/cleanup operations in tests with timeout larsxschneider
2015-11-06 9:28 ` Eric Sunshine
2015-11-06 9:47 ` Lars Schneider
2015-11-06 13:19 ` Lars Schneider
2015-11-06 8:58 ` [PATCH v4 4/4] Add Travis CI support larsxschneider
2015-11-06 9:56 ` Eric Sunshine
2015-11-06 13:18 ` Lars Schneider
[not found] ` <22B2C2B1-9260-4EC0-A4C5-C7F7DDD388BA@gmail.com>
2015-11-06 13:20 ` Sebastian Schuberth
2015-11-06 13:28 ` Lars Schneider
2015-11-06 13:36 ` Sebastian Schuberth
2015-11-06 13:55 ` Lars Schneider
2015-11-06 13:57 ` Sebastian Schuberth
2015-11-06 14:08 ` Lars Schneider
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=1446800323-2914-1-git-send-email-larsxschneider@gmail.com \
--to=larsxschneider@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=avila.jn@gmail.com \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=luke@diamand.org \
--cc=sschuberth@gmail.com \
--cc=sunshine@sunshineco.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).