From: Martin Sebor <msebor@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: overseers@sourceware.org, gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: GCC Bugzilla (and other) timeouts
Date: Wed, 26 Feb 2020 16:25:00 -0000 [thread overview]
Message-ID: <9937a596-e419-0a6e-e765-36cb8e8c5611@gmail.com> (raw)
In-Reply-To: <CAH6eHdRu90P4ocF64Rv6aRQQWR1aA-DZPz=w_o4EaMyaZCxSuA@mail.gmail.com>
On 2/26/20 1:32 AM, Jonathan Wakely wrote:
> 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)
>
I use git+ssh (from our documentation):
$ git remote get-url origin
git+ssh://msebor@gcc.gnu.org/git/gcc.git
> 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).
Thanks for the confirmation. Sounds like it's a known problem and
it's just a coincidence that it's happening again as we near a GCC
release. I think I remember last year there was also a disk
problem, and ditto the year before then:
https://gcc.gnu.org/ml/gcc/2018-01/msg00125.html
Maybe we should proactively replace the disks every December ;-)
Martin
prev parent reply other threads:[~2020-02-26 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 18:25 Martin Sebor
2020-02-26 8:32 ` Jonathan Wakely
2020-02-26 14:42 ` Jason Merrill
2020-02-26 15:08 ` Frank Ch. Eigler
2020-02-26 16:25 ` Martin Sebor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9937a596-e419-0a6e-e765-36cb8e8c5611@gmail.com \
--to=msebor@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).