If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

mutt output is unreadable

RESOLVED WORKSFORME

Status

Testing Graveyard
Mozmill
RESOLVED WORKSFORME
6 years ago
a year ago

People

(Reporter: Jeff Hammel, Unassigned)

Tracking

Details

(Reporter)

Description

6 years ago
For instance:

<skipping over 500 lines>
TEST-PASS |
/home/jhammel/mozmill/src/mozmill/mutt/mutt/tests/js/restart/test_user_restart/test2.js
| testShutdownBeforeTimeout
INFO | Passed: 1
INFO | Failed: 0
INFO | Skipped: 0
Some tests were unsuccessful.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
No Python Failures
===========================================================================
Javascript Failures:
Exit 256: mozmill--console-level=DEBUG-m/tmp/tmplmUTOo.ini
--console-level=DEBUG -m /tmp/tmplmUTOo.ini

This gives me no way of diagnosing what went wrong.
So you left out the one line which actually caused a failure. Can you try again? Meanwhile the output should be way better.
(Reporter)

Comment 2

5 years ago
I'm going to close this since the output is radically changed for the better since I ticketed.  I'll open new bugs if there are any specific issues.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
(Assignee)

Updated

a year ago
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.