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

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

From
Junio C Hamano <gitster@pobox.com>
Date
May 2, 2017, 09:52 UTC
Message-ID
<CAPc5daUOQVu66RDspzScUjufJvLs7TUS0UtqTZjJ=5sMBuF=TQ@mail.gmail.com>
In-Reply-To
<C434AB60-F2BB-44A1-B40D-449EA27E2314@gmail.com>
On Mon, May 1, 2017 at 8:32 PM, Lars Schneider <larsxschneider@gmail.com> wrote:
Show 6 quoted lines
>>
>> this should make the Git for Windows build a bit more stable. We saw
>> a few 502's recently. E.g. https://travis-ci.org/git/git/jobs/226669324
>>
> Please don't move this to next, yet. This seems not to work as expected :-(
> https://travis-ci.org/git/git/jobs/227513693

Sure. I am wondering if your other one to run both asciidoc & asciidoctor tee'ed to log files should be ready to work on 'next', though.

Thanks.
Previous: Lars SchneiderNext: Lars Schneider
Message 3 of 4 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, Apr 29, 2017
  2. Lars SchneiderMay 1, 2017
  3. Junio C HamanoMay 2, 2017
  4. Lars SchneiderMay 2, 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.