Re: What's cooking in git.git (Apr 2013, #05; Mon, 15)

[Jeff King <peff@peff.net>]

On Tue, Apr 16, 2013 at 01:49:13AM +0200, Øyvind A. Holm wrote:

> > [1] I know you always test master before pushing it out, but I suspect
> >     you do not run the GIT_TEST_HTTPD tests. The failures are in t5541
> >     and t5551.
> 
> Ah, that explains why the test suite passed here, I built a new
> version an hour ago from current master (v1.8.2.1-418-gaec3f77,
> 2013-04-15 12:45:15 -0700), and no errors were found. I build new gits
> almost every day for testing purposes (master, and next and maint very
> often) on several machines with different setups, and of course also
> to have the newest version. I'd like to run as many tests as possible.
> Is there any list of environment variables or make directives
> available to enable most of them?

I don't think there's a master list anywhere. The simplest thing is
probably to run the whole suite and grep for skipped tests, each of
which should usually explain their reasoning for the skip. Like:

  make test | grep '# skip'

Note that this will turn up more than just environment variables to set.
It will also turn up missing programs you might need to install to run
the tests (e.g., we do not do subversion tests if svn is not installed).
Which is a good thing if you are trying for complete test coverage. But
it will also turn up useless things that are just fundamental to your
platform (e.g., you cannot do both the case-sensitive and the
case-insensitive filesystem tests).

Most of the tests are on by default, unless necessary programs are
missing or you explicitly disable them. GIT_TEST_HTTPD and
GIT_TEST_GIT_DAEMON seem to be the exceptions.

-Peff