Closed
Bug 771105
Opened 12 years ago
Closed 12 years ago
Allow expected leaks in crashtests
Categories
(Testing :: Reftest, enhancement)
Testing
Reftest
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: ayg, Unassigned)
References
Details
(I'm filing this under reftests because AFAIK, crashtests are basically a special type of reftest.) In bug 766025, there's an assertion failure, but the only test-case available to regression-test the failure also leaks. So a) I can't regression-test the crash (because the only test available will fail regardless of the crash), and b) I can't test the leak as an expected fail so that we'll know if it's fixed and have the test checked in. Could we have some way to mark a test as expected to leak, like we have expected assertions?
Not really, because leaks can't easily be attributed to a single test like assertions can. Can we just fix the leak? What's the bug # for that?
Reporter | ||
Comment 2•12 years ago
|
||
Ah, good point. Probably this has to be INVALID, then. There's no separate bug for the leak yet -- I could look into fixing it, but I have enough other stuff on my plate now that I don't expect to be able to get around to it soon.
Yeah, I don't think there's a reasonable way to do this. Given the current amount of test coverage, I'd rather not have a test for a single bug than give up the leak coverage for all our crashtests.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•