Closed Bug 893760 Opened 12 years ago Closed 12 years ago

Inconsistent log line prefixes output by various parts of mozharness

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 887888

People

(Reporter: emorley, Unassigned)

Details

(Whiteboard: [mozharness])

Most of the mozharness log output uses a format like: { 06:03:34 INFO - 2178 INFO TEST-PASS | /tests/dom/browser-element/mochitest/test_browserElement_oop_ReloadPostRequest.html | undefined 06:03:34 INFO - 2179 INFO TEST-PASS | /tests/dom/browser-element/mochitest/test_browserElement_oop_ReloadPostRequest.html | undefined 06:03:34 INFO - 2180 INFO TEST-PASS | /tests/dom/browser-element/mochitest/test_browserElement_oop_ReloadPostRequest.html | undefined } However certain steps use: https://tbpl.mozilla.org/php/getParsedLog.php?id=25283167&tree=Mozilla-Inbound { 06:11:14 INFO - DMError: Automation Error: Timeout in command activity 07/15/2013 06:11:14: INFO: DMError: Automation Error: Timeout in command activity 06:11:14 INFO - WARNING | leakcheck | refcount logging is off, so leaks can't be detected! 07/15/2013 06:11:14: INFO: WARNING | leakcheck | refcount logging is off, so leaks can't be detected! } ie: Sometimes omitting the date & also using a colon as a separator instead of a hyphen. We should be consistent - I don't mind which we use, as long as we do so across the board. The outcome will affect bug 892958.
s/omitting/including/
No longer blocks: 892958
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.