This is the mail archive of the
mailing list for the GCC project.
Re: GCC Bugzilla (and other) timeouts
- From: Jason Merrill <jason at redhat dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: Martin Sebor <msebor at gmail dot com>, overseers at sourceware dot org, gcc mailing list <gcc at gcc dot gnu dot org>
- Date: Wed, 26 Feb 2020 09:41:50 -0500
- Subject: Re: GCC Bugzilla (and other) timeouts
- References: <firstname.lastname@example.org> <CAH6eHdRu90P4ocF64Rv6aRQQWR1aA-DZPz=w_o4EaMyaZCxSuA@mail.gmail.com>
On Wed, Feb 26, 2020 at 3:39 AM Jonathan Wakely <email@example.com>
> On Tue, 25 Feb 2020 at 18:25, Martin Sebor wrote:
> > Bugzilla has been slow lately, and today to the point of timing out
> > (I see the same problem with Git). This seems to be a recurring theme
> > around the time of a GCC release. Is anyone else experiencing this
> > problem and if so, does anyone know what the cause it and an ETA for
> > a solution? Is the upcoming hardware upgrade expected to solve it?
> > Thanks
> > Martin
> > $ git pull
> > Connection closed by 184.108.40.206 port 22
> > fatal: Could not read from remote repository.
> > Please make sure you have the correct access rights
> > and the repository exists.
> What URL are you using to pull? (git remote get-url origin)
> Bugzilla and httpd are very slow, but I haven't had any git timeouts.
> If you're using anonymous access that gets throttled more aggressively
> than authenticated access (using git+ssh:// for the protocol).
Yes, I used to use git:// for pulls and ssh:// for pushes, but switched to
ssh:// for both because I was getting too many rejected connections.