From: Eric Sunshine <sunshine@sunshineco.com>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: Git List <git@vger.kernel.org>,
Sebastian Schuberth <sschuberth@gmail.com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Jean-Noel Avila <avila.jn@gmail.com>,
Luke Diamand <luke@diamand.org>,
David Turner <dturner@twopensource.com>
Subject: Re: [PATCH v4 4/4] Add Travis CI support
Date: Fri, 6 Nov 2015 04:56:17 -0500 [thread overview]
Message-ID: <CAPig+cSc+BBgd3-UeVE79D9GWXfaQqbLCQdKo6FbhnPMsK_eFA@mail.gmail.com> (raw)
In-Reply-To: <1446800323-2914-5-git-send-email-larsxschneider@gmail.com>
On Fri, Nov 6, 2015 at 3:58 AM, <larsxschneider@gmail.com> wrote:
> The tests are currently executed on "Ubuntu 12.04 LTS Server Edition
> 64 bit" and on "OS X Mavericks" using gcc and clang.
>
> Perforce and Git-LFS are installed and therefore available for the
> respective tests.
>
> Signed-off-by: Lars Schneider <larsxschneider@gmail.com>
> ---
> diff --git a/.travis.yml b/.travis.yml
> @@ -0,0 +1,131 @@
> + matrix:
> + -
> + # NO_ICONV=YesPlease
> + - >
> + NO_CURL=YesPlease
> + NO_D_INO_IN_DIRENT=YesPlease
> + NO_DEFLATE_BOUND=YesPlease
> + NO_EXPAT=YesPlease
> + NO_GECOS_IN_PWENT=YesPlease
> + NO_GETTEXT=YesPlease
> + NO_HMAC_CTX_CLEANUP=YesPlease
> + NO_HSTRERROR=YesPlease
> + NO_INET_NTOP=YesPlease
> + NO_INET_PTON=YesPlease
> + NO_INITGROUPS=YesPlease
> + NO_INTTYPES_H=YesPlease
> + NO_IPV6=YesPlease
> + NO_IPV6=YesPlease
> + NO_LIBGEN_H=YesPlease
> + NO_MEMMEM=YesPlease
> + NO_MKDTEMP=YesPlease
> + NO_MKSTEMPS=YesPlease
> + NO_MMAP=YesPlease
> + NO_NSEC=YesPlease
> + NO_OPENSSL=YesPlease
> + NO_PERL=YesPlease
> + NO_PTHREADS=YesPlease
> + NO_REGEX=YesPlease
> + NO_SETENV=YesPlease
> + NO_SETITIMER=YesPlease
> + NO_SOCKADDR_STORAGE=YesPlease
> + NO_STRCASESTR=YesPlease
> + NO_STRLCPY=YesPlease
> + NO_STRTOUMAX=YesPlease
> + NO_STRUCT_ITIMERVAL=YesPlease
> + NO_SYMLINK_HEAD=YesPlease
> + NO_SYS_POLL_H=YesPlease
> + NO_SYS_SELECT_H=YesPlease
> + NO_UINTMAX_T=YesPlease
> + NO_UNSETENV=YesPlease
Hmm, aren't you losing test coverage by disabling some of these? Is
that desirable for continuous integration testing? Am I missing
something?
next prev parent reply other threads:[~2015-11-06 9:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 8:58 [PATCH v4 0/4] Add Travis CI support larsxschneider
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 [this message]
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=CAPig+cSc+BBgd3-UeVE79D9GWXfaQqbLCQdKo6FbhnPMsK_eFA@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=avila.jn@gmail.com \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=luke@diamand.org \
--cc=sschuberth@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).