Re: [PATCH v1 2/2] travis-ci: enable sequential test execution for t9113 and 9126

Eric Wong writes: > Junio C Hamano wrote: >> Lars Schneider writes: >> >> On 19 May 2016, at 19:11, Junio C Hamano wrote: >> >> Eric Wong writes: >> >> >> >>> Anyways, how about making the tests

Re: [PATCH v1 2/2] travis-ci: enable sequential test execution for t9113 and 9126

Junio C Hamano wrote: > Lars Schneider writes: > >> On 19 May 2016, at 19:11, Junio C Hamano wrote: > >> Eric Wong writes: > >> > >>> Anyways, how about making the tests run on separate ports and > >>> not worry

Re: [PATCH v1 2/2] travis-ci: enable sequential test execution for t9113 and 9126

Lars Schneider writes: >> On 19 May 2016, at 19:11, Junio C Hamano wrote: >> >> Eric Wong writes: >> >>> Anyways, how about making the tests run on separate ports and >>> not worry about serializing them at all? >> >> Yeah, that

Re: [PATCH v1 2/2] travis-ci: enable sequential test execution for t9113 and 9126

Lars Schneider wrote: > > On 19 May 2016, at 19:11, Junio C Hamano wrote: > > Eric Wong writes: > > > >> Anyways, how about making the tests run on separate ports and > >> not worry about serializing them at all? > > > > Yeah, that

Re: [PATCH v1 2/2] travis-ci: enable sequential test execution for t9113 and 9126

> On 19 May 2016, at 19:11, Junio C Hamano wrote: > > Eric Wong writes: > >> Anyways, how about making the tests run on separate ports and >> not worry about serializing them at all? > > Yeah, that does sound like a more sensible approach. Makes sense.

Re: [PATCH v1 2/2] travis-ci: enable sequential test execution for t9113 and 9126

Eric Wong writes: > Anyways, how about making the tests run on separate ports and > not worry about serializing them at all? Yeah, that does sound like a more sensible approach. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to

Re: [PATCH v1 2/2] travis-ci: enable sequential test execution for t9113 and 9126

larsxschnei...@gmail.com wrote: > Enable t9113 and 9126 by defining the SVNSERVER_PORT. Since both tests > open the same port during execution, they cannot run in parallel. Add > a ".seq.sh" suffix to the test files and teach "prove" to run them > sequentially. Interesting, I guess I forgot the