Closed
Bug 592262
Opened 14 years ago
Closed 13 years ago
Make valgrinding a try choice
Categories
(Release Engineering :: General, defect, P4)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 631838
People
(Reporter: davidb, Unassigned)
Details
(Whiteboard: [tryserver][q4-goal?])
As per #developers discussion just now on the topic of oranges. Edited for size: catlee: would automated valgrind runs help at all? ted: catlee: depends on the cause of the orange davidb_sheriff: catlee: i like that idea khuey: can we do automated valgrind runs fast enough to keep up? ted: beltzner: but we should probably improve our tooling or whatever we need to do to be able to pinpoint the causes of orange better jmaher: yeah, valgrind on unittests is a painful process catlee: well, probably not per checkin catlee: but a few times a day maybe? if there are spare cyles davidb_sheriff: catlee: maybe it could be a try choice? catlee: yeah, could be
Comment 1•14 years ago
|
||
It doesn't seem like anyone will have time to work on this quarter. I've put this in our potential q4 goals list and attached it to the bug tracking enhancements to try so that this will come up again for assignment.
Blocks: try_enhancements
Whiteboard: [tryserver][q4-goal?]
Updated•14 years ago
|
Priority: -- → P4
Updated•13 years ago
|
No longer blocks: try_enhancements
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•