Open
Bug 309823
Opened 19 years ago
Updated 1 year ago
Logfile from runtests.sh fills up with Terminated messages when using bash
Categories
(NSPR :: NSPR, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: jason.m.reid, Unassigned)
Details
Problem first found with Linux tests. Problem duplicated on Solaris 5.9 with /usr/bin/bash. TEST_TIMEOUT was set to 60. mace[svbld]:/share/builds/mccrel3/security/securitytip/builds/20050923.1/wozzeck_Solaris8/mozilla/nsprpub/SunOS5.8_64_DBG.OBJ/pr/tests> /usr/bin/bash ./runtests.sh NSPR Test Results - tests BEGIN Fri Sep 23 16:06:40 PDT 2005 NSPR_TEST_LOGFILE /dev/null Test Result accept Passed acceptread./runtests.sh: line 272: 22061 Terminated ( sleep $TEST_TIMEOUT; kill $test_pid >/dev/null 2>&1 ) Passed acceptreademu./runtests.sh: line 272: 22066 Terminated ( sleep $TEST_TIMEOUT; kill $test_pid >/dev/null 2>&1 ) Passed affinity./runtests.sh: line 272: 22072 Terminated ( sleep $TEST_TIMEOUT; kill $test_pid >/dev/null 2>&1 ) Passed mace[svbld]:/u/svbld/ns/securityqa/nightly/solaris> ptree 22054 329 /usr/lib/ssh/sshd 17668 /usr/lib/ssh/sshd 17670 -tcsh 22054 /usr/bin/bash ./runtests.sh 22065 ./acceptread 22066 /usr/bin/bash ./runtests.sh 22067 sleep 60 Using bash, when runtests.sh kills the subshell containing the sleep process, a Terminated message is printed. This behaviour does not occur when using the Bourne shell. The created impression which is erronous is that the test script is killing every test and falsely reporting passes. This behavious makes it difficult to detect after the fact if runtest.sh did need to terminate a hanging test case.
Updated•18 years ago
|
QA Contact: wtchang → nspr
Updated•2 years ago
|
Severity: minor → S4
Comment 1•1 year ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: wtc → nobody
You need to log in
before you can comment on or make changes to this bug.
Description
•