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

Mochitests should fail on exceeding an Rlk-style leak threshold

RESOLVED FIXED

Status

Testing
Mochitest
--
major
RESOLVED FIXED
10 years ago
9 years ago

People

(Reporter: Waldo, Assigned: Waldo)

Tracking

({autotest-issue})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Created attachment 305386 [details] [diff] [review]
Short and sweet, will need tinderbox-side changes to actually check leak thresholds

We already sorta did this in bug 397724, but there are too many changes going on at once on the tinderboxen set up on the Testing tree to reasonably work with this, so we need a lighter-weight solution.
Attachment #305386 - Flags: review?(sayrer)

Updated

10 years ago
Attachment #305386 - Flags: review?(sayrer) → review+
Depends on: 417943
Landed, with removal of |else: pass| and with a change of the error message if "0 TOTAL" not found to use ERROR FAIL since that's what the log-scraping code uses.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Flags: in-testsuite-
Component: Testing → Mochitest
Flags: in-testsuite-
Product: Core → Testing
QA Contact: testing → mochitest
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.