Closed
Bug 661245
Opened 13 years ago
Closed 9 years ago
Handle errors when gathering metrics
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: davehunt, Unassigned, Mentored)
References
Details
(Whiteboard: [endurance][lang=js][good first bug])
In bug 656869, Nick Nethercote noted that there may be issues calculating the explicit memory due to the heapUsed having a value of -1. We need to have a way to handle these issues and log messages for later displaying in the reports.
Updated•11 years ago
|
Whiteboard: [mozmill-endurance] → [endurance][mentor=davehunt][lang=js][good first bug]
Assignee | ||
Updated•10 years ago
|
Mentor: dave.hunt
Whiteboard: [endurance][mentor=davehunt][lang=js][good first bug] → [endurance][lang=js][good first bug]
I want to solve it. May it assign to me? Btw, do I have a mentor? Because I am newbie in solving bugs in open source project. Thanks!
Reporter | ||
Comment 2•9 years ago
|
||
The endurance tests are no longer active, and we should have closed this bug a while ago. Sorry for the confusion, I hope you find something else to work on.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(dave.hunt)
QA Contact: hskupin
Resolution: --- → WONTFIX
Updated•5 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•