Open
Bug 487196
Opened 15 years ago
Updated 1 year ago
Strsclnt doesn't wait for selfserv in memleak.sh.
Categories
(NSS :: Test, defect, P3)
Tracking
(Not tracked)
NEW
3.11.11
People
(Reporter: slavomir.katuscak+mozilla, Unassigned)
References
Details
Testing scenario used in memleak.sh: 1. start selfserv as background process 2. wait 5 seconds 3. start strsclnt tests In some cases there can happen that selfserv needs more than 5 seconds to start and then strsclnt fails: memleak.sh: -------- Running selfserv under Valgrind: /usr/bin/valgrind --tool=memcheck --leak-check=yes --show-reachable=yes --partial-loads-ok=yes --leak-resolution=high --num-callers=50 selfserv -D -p 8111 -d /export/tinderlight/data/doyoga_32_DBG/mozilla/tests_results/security/doyoga.1/server_memleak -n doyoga.red.iplanet.com -e doyoga.red.iplanet.com-ec -w nss -c ABCDEF:C001:C002:C003:C004:C005:C006:C007:C008:C009:C00A:C00B:C00C:C00D:C00E:C00F:C010:C011:C012:C013:C014cdefgijklmnvyz -t 5 memleak.sh: -------- Trying cipher A: strsclnt -q -p 8111 -d /export/tinderlight/data/doyoga_32_DBG/mozilla/tests_results/security/doyoga.1/client_memleak -w nss -c 1000 -n TestUser doyoga.red.iplanet.com -C A strsclnt: Client timed out waiting for connection to server. memleak.sh server-32-libfreebl_3-NORMAL: Strsclnt produced a returncode of 1 - FAILED memleak.sh: -------- Trying cipher B: strsclnt -q -p 8111 -d /export/tinderlight/data/doyoga_32_DBG/mozilla/tests_results/security/doyoga.1/client_memleak -w nss -c 1000 -n TestUser doyoga.red.iplanet.com -C B strsclnt: Client timed out waiting for connection to server. memleak.sh server-32-libfreebl_3-NORMAL: Strsclnt produced a returncode of 1 - FAILED memleak.sh: -------- Trying cipher C: strsclnt -q -p 8111 -d /export/tinderlight/data/doyoga_32_DBG/mozilla/tests_results/security/doyoga.1/client_memleak -w nss -c 1000 -n TestUser doyoga.red.iplanet.com -C C strsclnt: Client timed out waiting for connection to server. memleak.sh server-32-libfreebl_3-NORMAL: Strsclnt produced a returncode of 1 - FAILED memleak.sh: -------- Trying cipher D: strsclnt -q -p 8111 -d /export/tinderlight/data/doyoga_32_DBG/mozilla/tests_results/security/doyoga.1/client_memleak -w nss -c 1000 -n TestUser doyoga.red.iplanet.com -C D strsclnt: -- SSL: Server Certificate Validated. strsclnt: 0 cache hits; 0 cache misses, 0 cache not reusable strsclnt: SSL2 - 1 server certificates tested.
Reporter | ||
Updated•15 years ago
|
Priority: -- → P3
Comment 1•15 years ago
|
||
This seems like a shell script problem, not a strsclnt problem. The tstclnt program has an option to wait for the server to be ready. If this problem with absurd start-up times cannot be solved, then you should use tstclnt after starting selfserv and before starting strsclnt, to ensure that selfserv is running.
Reporter | ||
Comment 2•15 years ago
|
||
I agree, it's problem in memleak.sh, I plan to add there some check whether selfserv is started.
Updated•2 years ago
|
Severity: normal → S3
Comment 3•1 year ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: slavomir.katuscak+mozilla → nobody
You need to log in
before you can comment on or make changes to this bug.
Description
•