David Chisnall 76aa2ef017 Fix a bug in mutex_try_to_lock. This was previously trying to unlock a mutex that it didn't own, causing an assertion failure in mutex.cpp. The issue was that the unique_lock went out of scope, releasing the lock on m, then m.unlock() was called on an already-unlocked mutex. ...

This change removes the spurious m.unlock() call.  

If this test was previously passing for anyone with assertions enabled, then they should investigate bugs in their pthread implementation, as pthread_unlock() should not return 0 if the mutex is currently unlocked.



git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@175506 91177308-0d34-0410-b5e6-96231b3b80d8

2013-02-19 11:28:45 +00:00

..

copy_assign.fail.cpp

license change

2010-11-16 22:09:02 +00:00

copy_ctor.fail.cpp

license change

2010-11-16 22:09:02 +00:00

default.pass.cpp

license change

2010-11-16 22:09:02 +00:00

move_assign.pass.cpp

license change

2010-11-16 22:09:02 +00:00

move_ctor.pass.cpp

license change

2010-11-16 22:09:02 +00:00

mutex_adopt_lock.pass.cpp

license change

2010-11-16 22:09:02 +00:00

mutex_defer_lock.pass.cpp

license change

2010-11-16 22:09:02 +00:00

mutex_duration.pass.cpp

Give a lot more timing latitude to some of the timing tests. Busy buildbots are hitting the timing limits too often.

2013-02-06 20:25:56 +00:00

mutex_time_point.pass.cpp

[tests] Increase a bunch of wait limits.

2013-02-08 17:41:19 +00:00

mutex_try_to_lock.pass.cpp

Fix a bug in mutex_try_to_lock. This was previously trying to unlock a mutex that it didn't own, causing an assertion failure in mutex.cpp. The issue was that the unique_lock went out of scope, releasing the lock on m, then m.unlock() was called on an already-unlocked mutex.

2013-02-19 11:28:45 +00:00

mutex.pass.cpp

[tests] Increase a bunch of wait limits.

2013-02-08 17:41:19 +00:00