Opened 7 weeks ago

Closed 7 weeks ago

#19232 closed bug (fixed)

pthread_cond improvement

Reported by: cocobean Owned by: nobody
Priority: normal Milestone: R1/beta6
Component: System/POSIX Version: R1/beta5
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

pthread_cond implementation in Haiku R1b5 must pass these OpenPOSIX tests for UNIX 03/POSIX.1-2008 mandatory compliance: 

conformance/interfaces/pthread_cond_init/2-2: execution: FAILED 
conformance/interfaces/pthread_cond_timedwait/2-6: execution: FAILED 
conformance/interfaces/pthread_cond_wait/2-3: execution: FAILED

Change History (1)

comment:1 by waddlesplash, 7 weeks ago

Milestone: Unscheduled → R1/beta6
Resolution: → fixed
Status: new → closed

There is no "2-2" init test. There is 4-1, which fails because setrlimit does. We don't really implement it, but it seems it can fail for a variety of reasons in POSIX, one of which is: 

[EINVAL]
    The limit specified cannot be lowered because current usage is already higher than the limit.

So I don't think we need to do anything for that.

pthread_cond_timedwait/2-6 and pthread_cond_wait/2-3 fixed in hrev58306. pthread_cond_wait/pthread_cond_wait_4-1 fails because it tries to use an uninitialized mutex, but that appears to be a bug in the test.

Note: See TracTickets for help on using tickets.