git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Lars Schneider <larsxschneider@gmail.com>
Date
Nov 11, 2016, 08:22 UTC
Message-ID
<2088B631-4FE8-4232-9F3C-699122E6A7B0@gmail.com>
In-Reply-To
<20161110161012.jube4bwbww2wa2ew@sigill.intra.peff.net>
On 10 Nov 2016, at 17:10, Jeff King <peff@peff.net> wrote:
Show 21 quoted lines
> 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
>>> written around HTTP::Server::Simple or something).
>>> 
>>> On the other hand, testing against Apache approximates a more real-world
>>> case, which has value. It might be nice if our tests supported multiple
>>> web servers, but that would mean duplicating the config for each
>>> manually.
>> 
>> I agree that the real-world Apache test is more valuable and I really want
>> to keep the Linux Apache test running. However, I don't think many people
>> use macOS as Git web server and therefore I thought it is not worth the
>> effort to investigate this problem further.
> 
> 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. :)
Well, I haven't seen it from that perspective, yet, but I agree :-)

To all macOS users on the list: Does anyone execute the tests with GIT_TEST_HTTPD enabled successfully?

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 TravisCI client tests could go against these servers.

I realize that this idea is probably unrealistic because too much setup and maintenance work would be required.

Cheers, Lars

Previous: Jeff KingNext: Jeff King
Message 22 of 35 in “Fix default macOS build locally and on Travis CI”
  1. 0/2 Fix default macOS build locally and on Travis CIlarsxschneider@gmail.com, Oct 17, 2016
  2. 1/2 config.mak.in: set NO_OPENSSL and APPLE_COMMON_CRYPTO for macOS >10.11larsxschneider@gmail.com, Oct 17, 2016
  3. Jeff KingOct 17, 2016
  4. Lars SchneiderNov 6, 2016
  5. Jeff KingNov 7, 2016
  6. Paul SmithNov 7, 2016
  7. Jeff KingNov 7, 2016
  8. Paul SmithNov 7, 2016
  9. Torsten BögershausenNov 9, 2016
  10. Lars SchneiderNov 9, 2016
  11. Torsten BögershausenNov 9, 2016
  12. Makefile: set NO_OPENSSL on macOS by defaultlarsxschneider@gmail.com, Nov 10, 2016
  13. 2/2 travis-ci: disable GIT_TEST_HTTPD for macOSlarsxschneider@gmail.com, Oct 17, 2016
  14. Lars SchneiderNov 6, 2016
  15. Jeff KingNov 7, 2016
  16. Lars SchneiderNov 10, 2016
  17. Jeff KingNov 10, 2016
  18. Junio C HamanoNov 10, 2016
  19. Jeff KingNov 10, 2016
  20. Junio C HamanoNov 10, 2016
  21. Jeff KingNov 10, 2016
  22. Lars SchneiderNov 11, 2016
  23. Jeff KingNov 11, 2016
  24. Lars SchneiderNov 11, 2016
  25. Jeff KingNov 11, 2016
  26. Heiko VoigtNov 15, 2016
  27. Lars SchneiderNov 15, 2016
  28. Jeff KingNov 15, 2016
  29. Heiko VoigtNov 16, 2016
  30. Torsten BögershausenNov 16, 2016
  31. Junio C HamanoNov 9, 2016
  32. Torsten BögershausenNov 10, 2016
  33. Lars SchneiderNov 10, 2016
  34. Junio C HamanoNov 10, 2016
  35. Lars SchneiderNov 11, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.