TBPL should no longer match against "Thread N (crashed)"

RESOLVED FIXED

Status

Tree Management Graveyard
TBPL
RESOLVED FIXED
5 years ago
3 years ago

People

(Reporter: emorley, Assigned: emorley)

Tracking

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Now that PROCESS-CRASH works across correctly across the board (cpp unit-tests and talos using mozcrash, mochitest and reftest using automationutils.py), we shouldn't ever get a "Thread N (crashed)" without also having a "PROCESS-CRASH".

Philor, your memory is much better than mine - am I overlooking anything?
(Assignee)

Comment 1

5 years ago
Created attachment 703274 [details] [diff] [review]
Patch v1
Attachment #703274 - Flags: review?(philringnalda)
Comment on attachment 703274 [details] [diff] [review]
Patch v1

I think so, probably, I guess.
Attachment #703274 - Flags: review?(philringnalda) → review+
(Assignee)

Updated

5 years ago
Depends on: 833358
(Assignee)

Comment 4

5 years ago
In production.
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.