Closed
Bug 539950
Opened 15 years ago
Closed 14 years ago
Selfserv memory leak tests sometimes produces empty logfile.
Categories
(NSS :: Test, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
3.12.6
People
(Reporter: slavomir.katuscak+mozilla, Assigned: slavomir.katuscak+mozilla)
Details
Attachments
(1 file)
|
938 bytes,
patch
|
christophe.ravel.bugs
:
review+
|
Details | Diff | Splinter Review |
All memory leak tests should produce log files with all found stacks. On some machines logs from selfserv tests are empty. After troubleshooting I found out, that kill command that is run to ensure that selfserv is turned off sometimes runs too early before output from dbx tool is stored to logfile.
|
Assignee | |
Updated•15 years ago
|
Assignee: nobody → slavomir.katuscak
Priority: -- → P2
Target Milestone: --- → 3.12.6
|
|
Assignee | |
Comment 1•15 years ago
|
||
I tried to using sleep 5 command to delay kill, but this was not enough to produce log file from DBX, so I rather used sleep 20, to have there some reserve. It is enough to use this delay in run_strsclnt (in this case selfserv is under debugger). Function run_strsclnt_dbg uses kill command on selfserv too, but in this case selfserv is not under debugger so no logs are produced.
Attachment #421842 -
Flags: review?(christophe.ravel.bugs)
|
||
Comment 2•15 years ago
|
||
Comment on attachment 421842 [details] [diff] [review] Patch. r=christophe
Attachment #421842 -
Flags: review?(christophe.ravel.bugs) → review+
|
|
Assignee | |
Comment 3•14 years ago
|
||
Checking in memleak.sh; /cvsroot/mozilla/security/nss/tests/memleak/memleak.sh,v <-- memleak.sh new revision: 1.38; previous revision: 1.37 done
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•