ABR Bugs

I had a look in Bugzilla and saw a long list of ABR bugs (“Automated bug report?”) that look like exceptions. From what I could see, there’s no stack trace included in the bug report, so it is of little or no value. Is there a stack trace included but I just don’t know where to look for it? Is this VASSAL feature broken?

Thus spake fil512:

I had a look in Bugzilla and saw a long list of ABR bugs (“Automated bug
report?”) that look like exceptions. From what I could see, there’s no
stack trace included in the bug report, so it is of little or no value.
Is there a stack trace included but I just don’t know where to look for
it? Is this VASSAL feature broken?

I haven’t had time to check that Bugzilla is receiving bug reports
correctly yet. There should be an errorLog with a stack trace for
each of these bug reports; if there isn’t, it’s not working.

I’m nearly done with getting news submission working again. I’ll
see about this next.

Regarding bug reports: Nobody’s looked at them (that I know of) for
about three months now. (This roughly coincides with when I started
the final site migration push and when Brent went on haitus.) If you
would like to help triage them, that would be greatly appreciated.
It’s possibly the most important thing you could do at this point.
(But wait for me to have a look at BZ first.)


J.

I am standing by ready to start triaging as soon as I get the sign from you that the ABR BZ process is functioning properly.

Thus spake fil512:

“uckelman” wrote:

If you would like to help triage them, that would be greatly
appreciated.
It’s possibly the most important thing you could do at this point.
(But wait for me to have a look at BZ first.)

J.

I am standing by ready to start triaging as soon as I get the sign from
you that the ABR BZ process is functioning properly.

I see that the errorLogs aren’t being attached to new bugs. Also I see that
importing the issues from SF didn’t work properly… This looks like more
than I can take care of before I return home, so don’t expect any movement
from me before Sunday.


J.

Thus spake Joel Uckelman:

I am standing by ready to start triaging as soon as I get the sign from
you that the ABR BZ process is functioning properly.

I see that the errorLogs aren’t being attached to new bugs. Also I see that
importing the issues from SF didn’t work properly… This looks like more
than I can take care of before I return home, so don’t expect any movement
from me before Sunday.

I’m working on this now. The reason that errorLogs aren’t being attached
to new bugs in BZ is that BZ’s XML-RPC interface doesn’t support adding
attachements yet. I need to rewrite the script to use the email interface
instead, which does handle attachments.


J.

Thus spake Joel Uckelman:

I’m working on this now. The reason that errorLogs aren’t being attached
to new bugs in BZ is that BZ’s XML-RPC interface doesn’t support adding
attachements yet. I need to rewrite the script to use the email interface
instead, which does handle attachments.

I’m finding it rather incredible that none of the Python or Perl modules
for working with Bugzilla support adding attachments. I do not relish
writing attachment support myself. Does anybody know of something which
does support adding attachments to Bugzilla bugs?


J.

How did it work on the old server?

It it possible to have bugzilla automatically pick up e-mail from a mailbox? Presumably if the email had an attachment, bugzilla would import the attachment from the e-mail automatically?

-K

Looks like the answer is “Yes”. From cvs.mandriva.com/cgi-bin/viewvc. … ml?view=co

“The mail interface is able to cope with MIME-attachments. People could for example add a logfile as a mail attachment, and it will appear in bugzilla as attachment. A comment for the attachment should be added, it will describe the attachment in bugzilla.”

Thus spake fil512:

“uckelman” wrote:

I’m finding it rather incredible that none of the Python or Perl
modules
for working with Bugzilla support adding attachments. I do not relish
writing attachment support myself. Does anybody know of something
which
does support adding attachments to Bugzilla bugs?

How did it work on the old server?

It didn’t. We didn’t have our own bug tracker before. We were using the
awful one on SF.


J.

Thus spake fil512:

It it possible to have bugzilla automatically pick up e-mail from a
mailbox? Presumably if the email had an attachment, bugzilla would
import the attachment from the e-mail automatically?

The email importer doesn’t handle attachments.


J.

Thus spake fil512:

Looks like the answer is “Yes”. From
cvs.mandriva.com/cgi-bin/viewvc. … ml?view=co[1]

The mail interface is able to cope with MIME-attachments. People could
for example add a logfile as a mail attachment, and it will appear in
bugzilla as attachment. A comment for the attachment should be added,
it will describe the attachment in bugzilla.

This is newer than the version of BZ that Fedora 13 ships, then. In
3.4, it’s not supported.


J.

Progress report: I have a working script now. Either tonight or tomorrow, barring unexpected disasters, I should be able to resync Bugzilla with the tracker on SF and start capturing new bug reports properly.

The script I ended up writing is an ugly hack. Fortunately, Bugzilla 3.7 supports adding attachments through its XML-RPC interface, so eventually we’ll be able to chuck this script and go back to the much nicer one I had before.

Are you going to delete all the bug reports in there now that are missing attachments?

Thus spake fil512:

“uckelman” wrote:

Progress report: I have a working script now. Either tonight or
tomorrow, barring unexpected disasters, I should be able to resync
Bugzilla with the tracker on SF and start capturing new bug reports
properly.

The script I ended up writing is an ugly hack. Fortunately, Bugzilla
3.7 supports adding attachments through its XML-RPC interface, so
eventually we’ll be able to chuck this script and go back to the much
nicer one I had before.

Are you going to delete all the bug reports in there now that are
missing attachments?

I’m going to delete all of the bugs except the two which were reported
by hand, and then repopulate from the tracker on SF.


J.

Alright, I think we’re ready to roll now.