Hi William, On Sat, Jun 13, 2020 at 03:13:06PM +0200, William Dauchy wrote: > Hi, > > On Thu, Jun 11, 2020 at 1:10 PM Willy Tarreau <[email protected]> wrote: > > Sure but what I wanted to say was that travis seems to be the only > > point experiencing such difficulties and we don't know how it works > > nor what are the rules in place. > > I don't know whether this is related to the issue described here but I just > had: > > $ git pull --rebase > fatal: unable to access 'http://git.haproxy.org/git/haproxy.git/': The > requested URL returned error: 502 > $ git pull --rebase > error: The requested URL returned error: 502 (curl_result = 22, > http_code = 502, sha1 = f38175cf6ed4d02132e6b21cbf643f73be5ee000) > error: Unable to find f38175cf6ed4d02132e6b21cbf643f73be5ee000 under > http://git.haproxy.org/git/haproxy.git > Fetching objects: 4529, done. > Cannot obtain needed commit f38175cf6ed4d02132e6b21cbf643f73be5ee000 > while processing commit ff0e8a44a4c23ab36b6f67c4052777ac908d4211. > error: fetch failed. > > Third try was ok though :/
Thanks for the info, I'll have a look. However the issue reported about travis was a connection error, which likely indicates a routing issue. Cheers, Willy
