Skip to Content.
Sympa Menu

sm-grimoire - Re: [SM-Grimoire] Gurus Bugzilla

sm-grimoire AT lists.ibiblio.org

Subject: Discussion of Spells and Grimoire items

List archive

Chronological Thread  
  • From: Hamish Greig <hgreig AT bigpond.net.au>
  • To: sm-grimoire AT lists.ibiblio.org
  • Subject: Re: [SM-Grimoire] Gurus Bugzilla
  • Date: Tue, 2 Dec 2003 16:10:02 +1100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 2 Dec 2003 15:11, Sergey A. Lipnevich wrote:
> Please, not the last one. Let's keep it a safe place for kids. All of
> the bugs are "fixme", "found" doesn't make sense I think. How about
> "bite-size" or "quickfix"?

QUICKFIX is fine by me, I have already marked some as FIXME (meaning, just do
what the summary says) but QUICKFIX is a better keyword.

> >Normally I look through the bug, find the error and use that error in the
> >summary. Occasionally the actual error isn't listed in the bug and I must
> >download, unzip and read the castlog.bz2.
>
> I hate attachments that make you download and open them. But isn't that
> correct that a huge part of the Prometheus output is pasted into the
> initial bug description?

prometheus is a good piece of software, but it isn't HAL :) it puts a lot of
data into its reports but then attaches the entire log from the cast/s just
for further reference. Sometimes the actual error is only in the attachment
for five+ reasons.
1) it failed an md5 check
2) cast went past the original error (file not found etc) and the bug shows
the related failure further into the cast
3) a depends syntax error (depends provides not correct)
4) something that stops the cast prematurely like a check for something in
BUILD and exit if it isn't found
5) a CONFIGURE query that awaits input from a non-existant user

The handling of these situations will be improved in the future I expect(I
have yet to fully come to terms with prometheus innards and Andrew is busy in
RL)

> >Probably 70% of the time the summary is the fix also.
> >Guru's *can* close bugs (with good reason) if they see them as invalid
> > after reassigning, but you must tell me (so I can add that spell to the
> > ignore list) or the same bug will keep being reported.
>
> OK. I'd volunteer for reviewing the bugs submitted via Prometheus, is
> there an easy way to filter out the new ones?

if you mean newly submitted then yes, they are all submitted automatically to
the prometheus component in bugzilla, marked as new, with me as owner and the
machines hostname and time of cast as summary.
then I scan them, change the summary and assign them to their section.
I have also been assigning a lot to myself if the section is un-guru-ed. But
I
think I will stop doing that (I have 60+ assigned to me ATM)
So the simple way to find new bugs is save a query for
prometheus component + new status.

> >Apologies in advance.
>
> I'm sure nobody would mind. Care to assign a random share of bugs to
> sergey AT sourcemage.org without looking at them?

I just turned all three machines off so I could finally track down a few
errors and get it stable(openmosix has released a new version 2.4.22-2 and a
patch has already been sent to their mail list, plus I think I want to set up
a proper ntp server so I can rule out clock sync as a problem and I want to
finish getting distcc ccache handling rewritten so the recursion errors in
our standard distcc setup go away). I think I have summarised all the bugs
already in the database though.
I won't re-assign anything specifically to you, you know best what your
capabilities are, so if you want to have a look at open bugs in test/stable
grimoire you should find a lot of work to keep you happy.
I should mention that we should be diligent about accepting ownership of bugs
we intend to work on, or someone may make your efforts wasted by beating you
to submitting a fix (sorry Oadae, I didn't know you were working on that I
promise! )


> >If you get assigned a bug that has
> >"file not recognized: File truncated
> >collect2: ld returned 1 exit status"
> >that is actually an error from my distcc/ccache/nfs/openmosix setup and
> > you should not try to fix it :)
>
> We'll have to fix you :-).

see above, I am trying to fix myself today/tomorrow/soon
:-)
Hopefully I have answered more questions than I have created
Hamish
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/zB6q8fSufZR6424RAippAJ0ZFpIYUR62UVn/K7/OblUrSSrJmwCeJ5my
9uG4MSo2ZfHNxYdu7s5Q77c=
=CPYK
-----END PGP SIGNATURE-----





Archive powered by MHonArc 2.6.24.

Top of Page