git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: larsxschneider@gmail.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH v1 2/2] travis-ci: enable sequential test execution for t9113 and 9126
Date: Thu, 19 May 2016 10:06:58 +0000	[thread overview]
Message-ID: <20160519100658.GA20225@dcvr.yhbt.net> (raw)
In-Reply-To: <1463649009-56941-3-git-send-email-larsxschneider@gmail.com>

larsxschneider@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 problem because had some
rules in config.mak to serialize them for many years, now :x

Anyways, how about making the tests run on separate ports and
not worry about serializing them at all?  Maybe there was a
reason we didn't do this years ago, but I forget...

But probably the best (but I guess more difficult) option is to
get svnserve+apache to do socket activation off a random port
bound by a parent process at startup.

  reply	other threads:[~2016-05-19 10:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19  9:10 [PATCH v1 0/2] travis-ci: enable Git SVN tests larsxschneider
2016-05-19  9:10 ` [PATCH v1 1/2] travis-ci: enable Git SVN tests t91xx on Linux larsxschneider
2016-05-19  9:10 ` [PATCH v1 2/2] travis-ci: enable sequential test execution for t9113 and 9126 larsxschneider
2016-05-19 10:06   ` Eric Wong [this message]
2016-05-19 17:11     ` Junio C Hamano
2016-05-22 10:10       ` Lars Schneider
2016-05-22 20:26         ` Eric Wong
2016-05-23 21:22         ` Junio C Hamano
2016-05-23 21:32           ` Eric Wong
2016-05-23 21:47             ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160519100658.GA20225@dcvr.yhbt.net \
    --to=e@80x24.org \
    --cc=git@vger.kernel.org \
    --cc=larsxschneider@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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).