Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

On 16.11.16 15:39, Heiko Voigt wrote: > On Tue, Nov 15, 2016 at 10:31:59AM -0500, Jeff King wrote: >> On Tue, Nov 15, 2016 at 01:07:18PM +0100, Heiko Voigt wrote: >> >>> On Fri, Nov 11, 2016 at 09:22:51AM +0100, Lars Schneider wrote: To all macOS users on the list: Does anyone execute

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

On Tue, Nov 15, 2016 at 10:31:59AM -0500, Jeff King wrote: > On Tue, Nov 15, 2016 at 01:07:18PM +0100, Heiko Voigt wrote: > > > On Fri, Nov 11, 2016 at 09:22:51AM +0100, Lars Schneider wrote: > > > To all macOS users on the list: > > > Does anyone execute the tests with GIT_TEST_HTTPD enabled

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

On Tue, Nov 15, 2016 at 01:07:18PM +0100, Heiko Voigt wrote: > On Fri, Nov 11, 2016 at 09:22:51AM +0100, Lars Schneider wrote: > > To all macOS users on the list: > > Does anyone execute the tests with GIT_TEST_HTTPD enabled successfully? > > Nope. The following tests fail for me on master:

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

> On 15 Nov 2016, at 13:07, Heiko Voigt wrote: > > On Fri, Nov 11, 2016 at 09:22:51AM +0100, Lars Schneider wrote: >> To all macOS users on the list: >> Does anyone execute the tests with GIT_TEST_HTTPD enabled successfully? > > Nope. The following tests fail for me on

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

On Fri, Nov 11, 2016 at 09:22:51AM +0100, Lars Schneider wrote: > To all macOS users on the list: > Does anyone execute the tests with GIT_TEST_HTTPD enabled successfully? Nope. The following tests fail for me on master: 5539, 5540, 5541, 5542, 5550, 5551, 5561, 5812. Cheers Heiko

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

On Fri, Nov 11, 2016 at 10:13:44AM +0100, Lars Schneider wrote: > > If you did want to have a more real-world network-based test, I think > > the right solution is not for GitHub to set up a bunch of mock servers, > > but to design client-side tests that hit the _real_ GitHub (or GitLab, > > or

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

On 11 Nov 2016, at 09:47, Jeff King wrote: > On Fri, Nov 11, 2016 at 09:22:51AM +0100, Lars Schneider wrote: > >> There would be an alternative way to approach the problem: >> Someone (GitHub?, BitBucket?, GitLab?, ...) could setup a bunch of webservers >> with popular

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

On Fri, Nov 11, 2016 at 09:22:51AM +0100, Lars Schneider wrote: > There would be an alternative way to approach the problem: > Someone (GitHub?, BitBucket?, GitLab?, ...) could setup a bunch of webservers > with popular configurations and a way to reset a clean test environment. Then > the

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

On 10 Nov 2016, at 17:10, Jeff King wrote: > On Thu, Nov 10, 2016 at 12:07:14PM +0100, Lars Schneider wrote: > >>> Using Apache in the tests has been the source of frequent portability >>> problems and configuration headaches. I do wonder if we'd be better off >>> using some

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

On Thu, Nov 10, 2016 at 01:49:52PM -0800, Junio C Hamano wrote: > Yes, I recall the IIS one raised and discussed at least twice on the > list in the past, and it sounded that we want some solution to that. The patches had some issues. I suspect the population of people who want to run a git

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

Jeff King writes: >> I however do not know what the universally available simplest dummy >> HTTP server would be. There probably are better alternative than >> Apache with distro-customized ways of configuration that we have to >> adjust. >> >> A solution around

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

On Thu, Nov 10, 2016 at 01:33:29PM -0800, Junio C Hamano wrote: > Jeff King writes: > > > IMHO, the value in the http tests is not testing the server side, but > > the client side. Without being able to set up a dummy HTTP server, we do > > not have any way to exercise the client

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

Jeff King writes: > IMHO, the value in the http tests is not testing the server side, but > the client side. Without being able to set up a dummy HTTP server, we do > not have any way to exercise the client side of git-over-http at all. > And people on macOS _do_ use that. :)

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

On Thu, Nov 10, 2016 at 12:07:14PM +0100, Lars Schneider wrote: > > Using Apache in the tests has been the source of frequent portability > > problems and configuration headaches. I do wonder if we'd be better off > > using some small special-purpose web server (even a short perl script > >

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

> On 07 Nov 2016, at 22:20, Jeff King wrote: > > On Sun, Nov 06, 2016 at 10:42:36PM +0100, Lars Schneider wrote: > >>> From: Lars Schneider >>> >>> TravisCI changed their default macOS image from 10.10 to 10.11 [1]. >>> Unfortunately the HTTPD tests

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

On Sun, Nov 06, 2016 at 10:42:36PM +0100, Lars Schneider wrote: > > From: Lars Schneider > > > > TravisCI changed their default macOS image from 10.10 to 10.11 [1]. > > Unfortunately the HTTPD tests do not run out of the box using the > > pre-installed Apache web

Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

> On 17 Oct 2016, at 02:25, larsxschnei...@gmail.com wrote: > > From: Lars Schneider > > TravisCI changed their default macOS image from 10.10 to 10.11 [1]. > Unfortunately the HTTPD tests do not run out of the box using the > pre-installed Apache web server anymore.