Closed
Bug 589580
(sisyphus-valgrind)
Opened 14 years ago
Closed 7 years ago
[meta] valgrind messages found using sisyphus unitest automation
Categories
(Testing Graveyard :: Sisyphus, defect)
Testing Graveyard
Sisyphus
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bc, Unassigned)
References
Details
(Keywords: meta, sec-other)
No description provided.
|
Reporter | |
Updated•13 years ago
|
Summary: valgrind messages found using sisyphus unitest automation → [meta] valgrind messages found using sisyphus unitest automation
|
|
Reporter | |
Updated•11 years ago
|
Group: core-security
|
|
Reporter | |
Comment 1•11 years ago
|
||
jseward, thought you would be interested in the new bugs I am filing based on the updated valgrind unit test runs.
|
||
Comment 2•11 years ago
|
||
(In reply to Bob Clary [:bc:] from comment #1)
> jseward, thought you would be interested in the new bugs I am filing based
> on the updated valgrind unit test runs.
Yes, I am. I am particularly interested to hear of any cases in which
it is suspected that Memcheck is incorrectly reporting undefinedness
errors. Those are rare nowadays, and often not hard to fix (in V).
How much coverage does your test automation get for the ARM/B2G specific
parts of Gecko?
|
|
Reporter | |
Comment 3•11 years ago
|
||
(In reply to Julian Seward from comment #2)
> How much coverage does your test automation get for the ARM/B2G specific
> parts of Gecko?
None that I know of. Just that covered by testing on Linux with jemalloc enabled.
|
||
Updated•9 years ago
|
Group: core-security → core-security-release
|
|
Reporter | |
Comment 4•7 years ago
|
||
We no longer run the unittests under valgrind in bughunter. resolving.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
|
||
Updated•6 years ago
|
Product: Testing → Testing Graveyard
|
|
||
Updated•4 years ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•