Closed
Bug 1890349
Opened 2 years ago
Closed 2 years ago
only check failure for crash signature to identify a crash, don't require "application crashed" string
Categories
(Tree Management :: Treeherder: Frontend, defect)
Tree Management
Treeherder: Frontend
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: aryx, Assigned: aryx)
Details
https://treeherder.mozilla.org/jobs?repo=autoland&revision=56daf0a3e72bc04ceb0b6d6a5e8b51b32333fe11&selectedTaskRun=W9PYZDpLQ42ltNnvzYMzXA.0 has the failure line
PROCESS-CRASH | CachingDatabaseConnection not thread-safe [@ nsAutoOwningEventTarget::AssertCurrentThreadOwnsMe] | /webdriver/tests/bidi/browsing_context/close/invalid.py
Until now, Treeherder expected a crash signature prefixed by "application crashed" to identify it as a crash. Only look for a crash signature instead.
| Assignee | ||
Comment 1•2 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•