If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Crashes due to test failures should look different from real crashes in TBPL

RESOLVED FIXED

Status

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

People

(Reporter: Justin Lebar (not reading bugmail), Unassigned)

Tracking

Dependency tree / graph

Details

(Reporter)

Description

7 years ago
Our test harness produces a crash upon test failure.  This intentional crash is indistinguishable from an unintentional crash which occurs after a test failure in TBPL without clicking through and examining the logs.

Intentional crashes should be very quiet, and unintentional crashes should be very loud.

cjones tells me this depends on bug 585187.
Not "depends on" in the sense of "we have to have bug 585187 to fix this"; we have another bug to suppress intentional crashes in the output altogether by cleaning them up.  However, with bug 585187 we would be able to scrape all the crash stacks and either display the IntentionalCrash ones differently or filter them altogether.
These dependent bugs should eliminate all of the PROCESS-CRASH output for crashes we expect.
Depends on: 539823, 642175, 652501
I think all the cases of intentional ignorable crashes won't cause a test failure now, and all other crashes will.  The ignorable crashes shouldn't show up on TBPL as orange or in the blue suggestions box any more.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Updated

3 years ago
Product: Webtools → Tree Management
(Assignee)

Updated

3 years ago
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.