385748 - Timetest test failed on Linux.

Status: NEW

(NSPR :: NSPR, defect, P3)

Description

[Slavomir Katuscak]

From nightly tests:
securityjes5/20070621.1/workout.1-Linux2.4_x86_glibc_PTH_DBG.OBJ

timetest./runtests.sh: line 272: 23214 Terminated              ( sleep $TEST_TIMEOUT; kill $test_pid >/dev/null 2>&1 )
			FAILED

BEGIN TEST: timetest

PR_ParseTimeString() incorrect
t is -1664496000000000, t2 is -1664496004000000, time string is Tue Apr 3 16:11:56 -0748 1917


END TEST: timetest

Comment 1

[Nelson Bolyard (seldom reads bugmail)]

If NSPR had a "test" component, this bug would get that component.

This bug, and the other NSPR bugs like it that were filed in the last few days,
seems to be a defect in the test program and/or test script itself,
or in the system configuration, rather than (or in addition to) a defect 
in the NSPR libraries.  

If there is a defect in the NSPR libraries, these test results do not 
clearly indicate that.  Many of these failures are not occurring in NSPR
test programs at all.  

Have the systems run out of some resource?  
Are they not able to start more processes because the Process table is full?  
Are the failures to start new threads due to the process table being full? 
(Does each thread have its own PID?) 

Comment 2

[Yury]

Similarly on FreeBSD:
PR_ParseTimeString() incorrect
t is -1664496000000000, t2 is -1664495960000000, time string is Wed Apr 4 05:31:40 +0531 1917

version 4.9.2

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee is inactive on Bugzilla, so the assignee is being reset.