Closed
Bug 363197
Opened 18 years ago
Closed 17 years ago
Add NSS leak checking to tinderbox
Categories
(NSS :: Test, enhancement, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
3.11.7
People
(Reporter: nelson, Assigned: slavomir.katuscak+mozilla)
References
Details
Attachments
(1 file)
1.61 KB,
patch
|
neil.williams
:
review+
nelson
:
superreview+
|
Details | Diff | Splinter Review |
It has been reported (bug 363184) that a recent NSS checkin has increased leakage, a serious regression. The only way it was discovered was through the Tinderbox for FireFox! FireFox's tinderbox includes much more information than simple pass/fail for the build and for a simple QA script. See it at http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox&hours=24&maxdate=1165472224&legend=1 Among many other useful things, it shows Lk:XXX (bytes leaked) This allows developers to see the effect of a checkin on leaks, immediately after it is first built. NSS's tinderbox should also have this feature. ASAP.
Assignee | ||
Comment 1•17 years ago
|
||
Tinderbox printing is already part of memleak script. This patch adds version info.
Attachment #265116 -
Flags: superreview?(nelson)
Attachment #265116 -
Flags: review?(neil.williams)
Comment 2•17 years ago
|
||
Comment on attachment 265116 [details] [diff] [review] Patch to print DBG/OPT version. Looks like it does the trick. Why don't the leak stats report for all the tinderboxes? We don't run leak checking on all of them?
Attachment #265116 -
Flags: review?(neil.williams) → review+
Reporter | ||
Comment 3•17 years ago
|
||
Comment on attachment 265116 [details] [diff] [review] Patch to print DBG/OPT version. Pls commit this on the trunk. If it goes OK, then when the branch opens, you can commit on the branch.
Attachment #265116 -
Flags: superreview?(nelson) → superreview+
Assignee | ||
Comment 4•17 years ago
|
||
> Looks like it does the trick. Why don't the leak stats report for all the
> tinderboxes? We don't run leak checking on all of them?
>
We have some Tinderboxes only for leak checking. It's because leak checking takes much more time than other tests.
Assignee | ||
Comment 5•17 years ago
|
||
Trunk: Checking in memleak.sh; /cvsroot/mozilla/security/nss/tests/memleak/memleak.sh,v <-- memleak.sh new revision: 1.5; previous revision: 1.4
Assignee | ||
Comment 6•17 years ago
|
||
Branch: Checking in memleak.sh; /cvsroot/mozilla/security/nss/tests/memleak/memleak.sh,v <-- memleak.sh new revision: 1.1.2.4; previous revision: 1.1.2.3 done
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•16 years ago
|
Priority: -- → P2
Target Milestone: --- → 3.11.7
You need to log in
before you can comment on or make changes to this bug.
Description
•