From: Jason Merrill <jason@redhat.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Martin Sebor <msebor@gmail.com>,
overseers@sourceware.org, gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: GCC Bugzilla (and other) timeouts
Date: Wed, 26 Feb 2020 14:42:00 -0000 [thread overview]
Message-ID: <CADzB+2nyVKGXWo-gYvcxM_OUkF0b5YqyowDobb711=bza_UTUA@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdRu90P4ocF64Rv6aRQQWR1aA-DZPz=w_o4EaMyaZCxSuA@mail.gmail.com>
On Wed, Feb 26, 2020 at 3:39 AM Jonathan Wakely <jwakely.gcc@gmail.com>
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)
>
> 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.
Jason
next prev parent reply other threads:[~2020-02-26 14:42 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 [this message]
2020-02-26 15:08 ` Frank Ch. Eigler
2020-02-26 16:25 ` Martin Sebor
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='CADzB+2nyVKGXWo-gYvcxM_OUkF0b5YqyowDobb711=bza_UTUA@mail.gmail.com' \
--to=jason@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=msebor@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).