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

Re: [PATCH v2] travis-ci: retry if Git for Windows CI returns HTTP error 502 or 503

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
May 4, 2017, 09:19 UTC
Message-ID
<alpine.DEB.2.21.1.1705041118190.4905@virtualbox>
In-Reply-To
<20170503215015.17949-1-larsxschneider@gmail.com>
Hi Lars,
On Wed, 3 May 2017, Lars Schneider wrote:
Show 5 quoted lines
> The Git for Windows CI web app sometimes returns HTTP errors of
> "502 bad gateway" or "503 service unavailable" [1]. We also need to
> check the HTTP content because the GfW web app seems to pass through
> (error) results from other Azure calls with HTTP code 200.
> Wait a little and retry the request if this happens.

Thanks. In theory, it would be better to fix the web app to pass through also the 502 error code, in practice I have a hard time finding the time to make it so ;-)

Therefore, I would be very much in favor of the current version of the patch.

Ciao, Dscho

Previous: Lars SchneiderNext: Junio C Hamano
Message 2 of 5 in “travis-ci: retry if Git for Windows CI returns HTTP error 502 or 503”
  1. travis-ci: retry if Git for Windows CI returns HTTP error 502 or 503Lars Schneider, May 3, 2017
  2. Johannes SchindelinMay 4, 2017
  3. Junio C HamanoMay 9, 2017
  4. Lars SchneiderMay 9, 2017
  5. Junio C HamanoMay 9, 2017

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.