Closed Bug 1481435 Opened 6 years ago Closed 11 months ago

Output "thread '...' panicked at" failure messages as log level ERROR not INFO

Categories

(Release Engineering :: Applications: MozharnessCore, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: aryx, Assigned: aryx)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

This is treated by Mozharness as failure:

https://dxr.mozilla.org/mozilla-central/rev/4e56a2f51ad739ca52046723448f3129a58f1666/testing/mozharness/mozharness/mozilla/testing/errors.py#129

At the moment, it doesn't get regarded as failure, e.g. at https://treeherder.mozilla.org/logviewer.html#?job_id=190706906&repo=autoland&lineNumber=7509

14:09:11     INFO -  PID 5828 | Executing test 'styleeditor/complicated.js'
14:09:11     INFO -  PID 5828 | [Child 1140, Chrome_ChildThread] WARNING: pipe error: 109: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 346
14:09:13     INFO -  PID 5828 | 'complicated.styleeditor.open.settle.DAMP' took 21.77295208707801ms.
14:09:13     INFO -  PID 5828 | Garbage collect
14:09:14     INFO -  PID 5828 | Reload page on 'complicated.styleeditor'
14:09:14     INFO -  PID 5828 | thread '<unnamed>' panicked at 'byte index 340423688 is out of bounds of `localhost:49753`', libcore\str\mod.rs:2094:9
14:09:14     INFO -  PID 5828 | stack backtrace:
14:09:14     INFO -  PID 5828 |    0: 0x654d5d40 - workerlz4_compress
14:09:14     INFO -  PID 5828 |    1: 0x654ce0e9 - workerlz4_compress
14:09:14     INFO -  PID 5828 | [Parent 5828, Gecko_IOThread] WARNING: pipe error: 232: file z:/build/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 513
14:09:14     INFO -  PID 5828 |
14:09:14     INFO -  PID 5828 | ###!!! [Parent][MessageChannel] Error: (msgtype=0x170089,name=PBrowser::Msg_UpdateNativeWindowHandle) Channel error: cannot send/recv
14:09:14     INFO -  PID 5828 |
14:09:14     INFO -  PID 5828 |
14:09:14     INFO -  PID 5828 | ###!!! [Parent][MessageChannel] Error: (msgtype=0x17007C,name=PBrowser::Msg_Destroy) Channel error: cannot send/recv
14:09:14     INFO -  PID 5828 |
14:09:14     INFO -  PID 5828 | [Parent 5828, Gecko_IOThread] WARNING: file z:/build/build/src/ipc/chromium/src/base/process_util_win.cc, line 188
14:14:11     INFO -  PID 5828 | TEST-UNEXPECTED-FAIL | damp | styleeditor/complicated.js: Test timed out

Treeherder: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=bc1d531d4e251d563f83877eefd454675eb81f2a&selectedJob=190706906
Hi!

It looks like the current mozharness error regex in `testing/mozharness/mozharness/mozilla/testing/errors.py` is broken, since that line is still being output as INFO not error. If that were fixed, Treeherder would pick this line up automatically. (And we're no longer accepting regex changes in Treeherder for cases where the test harness/runner should be using appropriate log line prefixes, so mozharness is where this needs to be fixed.)

ie:

14:09:14     INFO -  PID 5828 | thread '<unnamed>' panicked at 'byte index 340423688 is out of bounds of `localhost:49753`', libcore\str\mod.rs:2094:9

...should be output as:

14:09:14    ERROR -  PID 5828 | thread '<unnamed>' panicked at 'byte index 340423688 is out of bounds of `localhost:49753`', libcore\str\mod.rs:2094:9
Blocks: 778688
Component: Treeherder: Log Parsing & Classification → Applications: MozharnessCore
Product: Tree Management → Release Engineering
QA Contact: jlund
Summary: Treat "thread '...' panicked at" as failure messages → Output "thread '...' panicked at" failure messages as log level ERROR not INFO
Status: ASSIGNED → RESOLVED
Closed: 11 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: