Open
Bug 201405
Opened 21 years ago
Updated 2 years ago
The cvar2 test calls PR_WaitCondVar in if statements
Categories
(NSPR :: NSPR, defect)
Tracking
(Not tracked)
REOPENED
People
(Reporter: wtc, Unassigned)
Details
Attachments
(1 file)
|
926 bytes,
patch
|
Details | Diff | Splinter Review |
PR_WaitCondVar must always be called in a while loop. I am surprised to find out that the cvar2 test calls PR_WaitCondVar in if statements in two places. Sigh.
|
Reporter | |
Comment 1•21 years ago
|
||
|
|
Reporter | |
Comment 2•21 years ago
|
||
Fix checked into the tip of NSPR.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Whiteboard: [4.3.1]
Target Milestone: --- → 4.3
|
|
Reporter | |
Comment 3•21 years ago
|
||
Reopened the bug. The patch caused the cvar2.c test to hang in the timeout test, which expects the PR_WaitCondVar call to be called only once.
Status: RESOLVED → REOPENED
Priority: -- → P1
Resolution: FIXED → ---
Target Milestone: 4.3 → 4.4
|
|
Reporter | |
Updated•21 years ago
|
Whiteboard: [4.3.1]
Target Milestone: 4.4 → ---
|
||
Updated•18 years ago
|
QA Contact: wtchang → nspr
|
||
Comment 4•2 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months and this bug has priority 'P1'.
:KaiE, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: wtc → nobody
Flags: needinfo?(kaie)
|
||
Updated•2 years ago
|
Severity: normal → S4
Flags: needinfo?(kaie)
Priority: P1 → --
You need to log in
before you can comment on or make changes to this bug.
Description
•