Dan Albert c4bcc75f09 Clean up the pthread key tests.
The previous pthread_key_create_many test was really
pthread_key_create_all, which has proven very difficult to test
correctly (because it is affected by any other parts of the system using
pthread keys, and that can vary with test ordering). It also tested
expected values of PTHREAD_KEYS_MAX and the associated sysconf() value,
rather than those being in their own test.

Instead, split this test into a few distinct tests:

 * pthread.pthread_keys_max
 * pthread._SC_THREAD_KEYS_MAX_big_enough_for_POSIX
 * pthread.pthread_key_many_distinct
     * We actually didn't have a test to ensure that the keys we were
       creating were distinct.
 * pthread.pthread_key_EAGAIN
     * Make sure pthread_key_create() will _eventually_ fail with
       EAGAIN, not at a (sometimes incorrectly) predetermined maximum.

Change-Id: Iff1e4fdcc02404094bde0418122c64c227cf1702
2014-09-30 15:40:14 -07:00
..
2013-12-03 18:42:41 -08:00
2013-12-03 18:42:41 -08:00
2014-09-11 08:45:46 -07:00
2013-02-01 14:51:19 -08:00
2014-08-22 10:23:12 -07:00
2014-04-10 20:44:27 -07:00
2014-02-21 16:27:21 +00:00
2013-02-13 14:40:48 -08:00
2014-06-12 13:16:36 -07:00
2014-01-03 14:49:37 -08:00
2014-09-22 14:41:30 -07:00