Closed Bug 385752 Opened 18 years ago Closed 8 years ago

Perf test fails on HPUX.

Categories

(NSPR :: NSPR, defect, P3)

HP
HP-UX
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: slavomir.katuscak+mozilla, Assigned: slavomir.katuscak+mozilla)

Details

(Whiteboard: test)

From nightly tests: securitytip/20070622.1/charm.4-HP-UXB.11.11_64_OPT.OBJ perf./runtests.sh[261]: 15543 Terminated FAILED BEGIN TEST: perf CDThread: cannot create thread 297 CDThread: cannot create thread 298 CDThread: cannot create thread 299 CDThread: cannot create thread 300 ... CDThread: cannot create thread 997 CDThread: cannot create thread 998 CDThread: cannot create thread 999 ContextSwitch: cannot create thread ContextSwitch: cannot create thread END TEST: perf
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?)
Assignee: wtc → slavomir.katuscak
Whiteboard: test
This failure is specific to HP-UX. By default a process cannot create too many threads on HP-UX. We used to change some HP-UX kernel parameters to allow NSPR tests that create a lot of threads to pass. The proper fix is to change these tests to not create that many threads, or to handle the "out of resources" error from PR_CreateThread gracefully (without failing the test).
Priority: -- → P3
WONTFIX?
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.