This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Bugzilla timing out

From: "H.J. Lu" <hjl dot tools at gmail dot com>
To: Martin Sebor <msebor at gmail dot com>
Cc: "Frank Ch. Eigler" <fche at redhat dot com>, Eric Gallager <egall at gwmail dot gwu dot edu>, GCC Mailing List <gcc at gcc dot gnu dot org>
Date: Fri, 26 Jan 2018 13:55:06 -0800
Subject: Re: Bugzilla timing out
Authentication-results: sourceware.org; auth=none
References: <cf68f346-914e-2826-608f-ed9fe461f790@gmail.com> <87mv1b2d8m.fsf@redhat.com> <CAMfHzOsH-E68rRK-9krMU5wkBSCwcLF43zLTRtCZZTcLbcg3DA@mail.gmail.com> <20180122180859.GG19913@redhat.com> <e329c96e-d979-b216-c38c-903cea2a80ed@gmail.com>

On Fri, Jan 26, 2018 at 1:52 PM, Martin Sebor <msebor@gmail.com> wrote:
> On 01/22/2018 11:08 AM, Frank Ch. Eigler wrote:
>>
>> Hi -
>>
>>> Problems are still occurring for me; Bugzilla gives me 504 Gateway
>>> Time-outs when I try to access it tonight...
>>
>>
>> OK, we reworked some of the database routine maintenance workload,
>> e.g., a nightly cleanup pass that was quite likely excessive, and
>> will keep monitoring.
>
>
> Thanks for looking into it.  I'm still (or again) seeing very
> poor responsiveness.  Right now, bringing up an existing bug
> takes an entire minute.
>

Same here.  When I opened a new bug today, it timed out.  I had to look up
the database to see if I opened it or not.


-- 
H.J.

References:
- Bugzilla timing out
  - From: Martin Sebor
- Re: Bugzilla timing out
  - From: Frank Ch. Eigler
- Re: Bugzilla timing out
  - From: Eric Gallager
- Re: Bugzilla timing out
  - From: Frank Ch. Eigler
- Re: Bugzilla timing out
  - From: Martin Sebor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]