Closed Bug 584573 Opened 15 years ago Closed 14 years ago

Clean up logging code in mochitest

Categories

(Testing :: General, defect)

Product:
Testing
Component:
General
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: cmtalbert, Unassigned)

References

Details

There are two very small issues with logging in mochitest. If you specify remote-logfile and --logfile, the harness gets confused and doesn't run anything. If you don't specify a log file, our getFile in the cleanup step will throw a traceback because devicemanager::getfile will return none when getting the file and cause a traceback to be printed off of a string concatenation in devicemanager.py line 466. Patch forthcoming for both issues.
I have tested this with the checked in code in these scenarios: - "--remote-logfile=x.log --log-file=x2.log" - no logfile options, generates a mochitest.log on device and host - "--remote-logfile=y.log" (generates a mochitest.log on the host) - "--log-file=z.log" (generates a z.log on the host) This is fixed and works great.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Component: New Frameworks → General
You need to log in before you can comment on or make changes to this bug.