This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: What is wrong with Bugzilla? [Was: Re: GCC and Floating-Point]
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Michael Veksler <VEKSLER at il dot ibm dot com>
- Cc: Haren Visavadia <themis_hv at yahoo dot co dot uk>, gcc at gcc dot gnu dot org
- Date: Sun, 29 May 2005 23:48:39 -0400
- Subject: Re: What is wrong with Bugzilla? [Was: Re: GCC and Floating-Point]
- References: <OF6FF230B6.EECAD8D5-ON43257010.002C4681-43257010.003907E1@il.ibm.com>
On Sun, 2005-05-29 at 13:22 +0300, Michael Veksler wrote:
>
>
>
>
>
> Haren Visavadia wrote on 29/05/2005 10:51:00:
> >
> > You can search Bugzilla as well, so you do not fill in
> > duplicate bug report.
>
> Unfortunately, this is not 100% correct. Recently I have filed several
> duplicates, *after* searching Bugzilla.
> 1. There are too many ways to phrase a title, and too many
> times I search for wrong words.
>
> 2. The same bug may have several different user
> visible behaviors. You will end up with at least one
> duplicate per user visible behavior.
>
> At work, I maintain a bug database for my project and I
> sometimes need to fire-up a debugger to find out that
> a reported bug is a well known one.
>
> Many times only a trained developer (in the project) can assert
> that a PR is indeed a duplicate of another one.
>
> 3. Nontrivial search of GCC Bugzilla are, sometimes,
> extremely slow (over a minute). This inhibits multiple
> searches. I usually give up after the first one, and don't
> bother with a different type of query (which could have
> revealed a similar PR).
>
> >
Please send me the urls' to the buglists that are taking a long time to
generate (I don't care if they are a billion character long urls, i know
what to do with them :P)
I should be able to determine what will be necessary to make them go
faster.
--Dan