----- Original Message -----
On 02/15/2013 05:41 AM, Tadej Janež wrote:
> Hi!
>
> Here is an example:
>
https://bugzilla.redhat.com/show_bug.cgi?id=736498
> I filled this bug during the F-16 Graphics test week.
> After the Fedora EOL reminder and before the bug was closed, I
> tried to
> reproduce it on F-17 and I couldn't. Thus I marked the bug as
> CLOSED
> CURRENTRELEASE.
> After a couple of hours the Fedora EOL script changed the
> Resolution to
> WONTFIX:
>
https://bugzilla.redhat.com/show_activity.cgi?id=736498
>
> Another example:
>
https://bugzilla.redhat.com/show_bug.cgi?id=739315
> This is an ABRT bug report that was originally reported against
> gnome-shell on F-16. I encountered it with gnome-shell on F-17
> (
https://bugzilla.redhat.com/show_bug.cgi?id=739315#c72) and some
> people
> encountered it on F-18. I bumped the version to 18, however, after
> a
> couple of hours the Fedora EOL script closed it as WONTFIX.
>
> Could someone explain this behavior?
I wouldn't be surprised if whatever script is used to do the mass
closings
does a first pass generating the list of bugs that need closing, and
then does
a second pass closing them unconditionally. If someone changes the
bug info
between those two passes the script wouldn't notice. And figuring
that there
were probably thousand of bugs closed, it could very well take the
script
hours to run.
Exactly. The script uses CSV generated from Bugzilla in one time but
as the script runs nearly for a day, conflicts can happen...
This is all conjecture though, since I couldn't find any script
in
qa, releng,
or infrastructure git repos.
I got it from Spot, but yeah - it needs a new home. I'll take a look
what can I do (passwords and git does not work very well together ;-)
and where to put it.
Jaroslav
- Cole
--
devel mailing list
devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel