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

Lars Schneider writes: >>> It would be great if we could test this is a little bit in pu. >> >> This has been in 'pu' for a while. >> >> As the patch simply discards 502 (and others), it is unclear if the >> failing test on 'next' is now gone, or the attempt to run

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

> On 09 May 2017, at 07:31, Junio C Hamano wrote: > > Lars Schneider writes: > >> 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

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

Lars Schneider writes: > 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

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

Hi Lars, On Wed, 3 May 2017, Lars Schneider wrote: > 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

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

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