Re: USE_SHA1DC is broken in pu
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Mar 21, 2017, 20:09 UTC
- Message-ID
- <alpine.DEB.2.20.1703212105030.3767@virtualbox>
- In-Reply-To
- <FFC0EFBD-C4D9-4FB8-A45D-7B10689724A1@gmail.com>
Hi Lars,
On Fri, 17 Mar 2017, Lars Schneider wrote:
Show 11 quoted lines
> > On 17 Mar 2017, at 11:18, Lars Schneider <larsxschneider@gmail.com> > > wrote: > > > > Would it make sense/have value to add a job to our TravisCI build [1] > > that compiles Git in a few variations with some high profile switches > > such as USE_SHA1DC? Running all the tests for these variations would > > probably take to long but just compiling would be less than 2min per > > variation. > > ... or just run individual tests instead of the entire test suite for > these variations (e.g. only t0013 for the USE_SHA1DC variation).
The best solution may be to open a PR with .travis.yml patched to enable this flag. And then report back to he mailing list because the gentle people here are not that used to paying attention to Continuous Testing :-D
Ciao, Dscho