This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC Bugzilla (and other) timeouts
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: Martin Sebor <msebor at gmail dot com>
- Cc: overseers at sourceware dot org, gcc mailing list <gcc at gcc dot gnu dot org>
- Date: Wed, 26 Feb 2020 08:32:13 +0000
- Subject: Re: GCC Bugzilla (and other) timeouts
- References: <038bc19b-afd9-de7a-ff26-54ffa4d92b86@gmail.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 209.132.180.131 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).