From: Jonathan Nieder <jrnieder@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Shawn Pearce <spearce@spearce.org>,
Duy Nguyen <pclouds@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Use mongoose to test smart-http unconditionally?
Date: Wed, 4 Dec 2013 15:28:00 -0800 [thread overview]
Message-ID: <20131204232800.GG29959@google.com> (raw)
In-Reply-To: <20131204184842.GA11024@sigill.intra.peff.net>
Jeff King wrote:
> I don't know if it is worth all that much effort, though. I suppose it
> could get us more exposure to the httpd tests, but I do not know if it
> would be a good idea to turn them on by default anyway. They touch
> global machine resources (like ports) that can cause conflicts or test
> failures. I assume that is the reason we do not turn on git-daemon tests
> by default
Yup, that's why I don't run them.
For what it's worth, when I build git and run tests I tend to be in an
environment with apache available, but I'm too lazy to configure git's
tests to pick the right port and make sure it is reserved and so on.
Perhaps there's some way to help lazy people in the same boat? (E.g.,
picking a port randomly and skipping instead of failing a test when
it's taken or something)
next prev parent reply other threads:[~2013-12-04 23:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 10:53 Use mongoose to test smart-http unconditionally? Duy Nguyen
2013-12-04 18:13 ` Shawn Pearce
2013-12-04 18:48 ` Jeff King
2013-12-04 23:28 ` Jonathan Nieder [this message]
2013-12-05 0:18 ` Duy Nguyen
2013-12-05 3:00 ` Jeff King
2013-12-04 20:09 ` Junio C Hamano
2013-12-04 22:25 ` Jeff King
2013-12-04 22:53 ` Junio C Hamano
2013-12-05 2:49 ` Jeff King
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=20131204232800.GG29959@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=spearce@spearce.org \
/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).