Open
Bug 1796105
Opened 3 years ago
autoclassification: take assertion failures into account if they get logged before unexpected failure
Categories
(Tree Management :: Treeherder, defect)
Tree Management
Treeherder
Tracking
(Not tracked)
NEW
People
(Reporter: aryx, Unassigned)
Details
This task has an autoclassification with a bug as known failure.
The first 2 failure lines are:
SUMMARY: ThreadSanitizer: data race /builds/worker/fetches/sysroot-x86_64-linux-gnu/usr/lib/gcc/x86_64-linux-gnu/7.5.0/../../../../include/c++/7.5.0/bits/stl_tree.h:772:45 in _S_right
TEST-UNEXPECTED-FAIL | dom/media/webrtc/tests/mochitests/test_peerConnection_checkPacketDumpHook.html | Error in test execution: Error: Timeout waiting for rtp recv packet on level 1 timeout/<@https://example.com/tests/dom/media/webrtc/tests/mochitests/head.js:660:42 ...
Bug 1791550 is the suggestion for the second failure line and the autoclassification uses this for classification despite
- bug 1791550 having been resolved as incomplete 18h ago - it's incomplete, classification and not reopening might b expected at this implementation stage
- the assertion failure in the first line; this is the real issue.
No autoclassification should have been created in this case.
You need to log in
before you can comment on or make changes to this bug.
Description
•