Bugit should just attach I/O log as a file if the output is "too long."

Bug #1979389 reported by Doug Jacobs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bugit
New
Undecided
Unassigned

Bug Description

If you run Bugit and a Checkbox session is detected, you can choose to have Bugit include the I/O Log from the failed test you are writing a bug about. Bugit then pastes the log into the bug report body.

Most of the time the I/O Log is pretty short. However for some of the stress tests it can be very long. Very very long.

If the log is "too long" (>100 lines?) just attach it as a file instead pasting the entire thing into the bug. I was writing a bug for a stress test failure and the log file was over 3000 lines. It got pasted into the bug report's body and it was taking a very long time to scroll down through it all to get to the bottom half of the form. I don't know what would have happened if I tried submitting such a bug. It turns out, there was already a bug about this failure, so I just needed to update that bug, not file a new one.

Revision history for this message
Doug Jacobs (djacobs98) wrote :

Really long log file

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.