History log of /libcore/jsr166-tests/src/test/java/jsr166/LinkedTransferQueueTest.java
Revision Date Author Comments
9cb45b2153a3bf3950cd08f0084172ac794819ec 15-Mar-2016 Przemyslaw Szczepaniak <pszczepaniak@google.com> Fix for CollectionTest not running properly on vogar + missing tests

Made CollectionTest non-public, is shouldn't cause problems
with vogar anymore. Also, CTS currently doesn't find nested tests,
so I've moved some from the LinkedTransferQueueTest to
separate files.

Bug: 27673907
Change-Id: Iee6ecdee3128353f360ead7641cbafcb331f5644
(cherry picked from commit 7fe9db6dc16a8c5f58e1b4657967b71138e1f3ce)
e8b323c7cb7d55be9a4df579231e44f04f53d766 11-Mar-2016 Przemyslaw Szczepaniak <pszczepaniak@google.com> JSR-166 update without java 1.9 method/classes

Second attempt, in frist one I've submitted some code from openJdk 1.9
that shouldn't be here, orignial change can be found at
5328e07d282bef36ac8b757bbee16a761415b2c4

Adapted from sources taken from CVS using:
cvs -d ':pserver:anonymous@gee.cs.oswego.edu/home/jsr166/jsr166' checkout -D "03/03/2016 10:00:00 GMT" jsr166

This time with hidden/removed "@since 9" methods and classes

Bug: 27426599
Change-Id: Ibd8d26e13cba091bfd983c73d005e4f8d8f5946d
(cherry picked from commit b8b75116273ecfdb8ffdd1869b1c0dd04570a95e)
12b0b5bff9ecb10177ba7fa5e31248f986ad9a42 06-Jan-2016 Hiroshi Yamauchi <yamauchi@google.com> Temporarily wait without timeouts in two jsr166 tests for debugging.

To help figure out whether a locally non-reproducible but
buildbot-reproducible test failure is a timeout issue or something else,
change the wait code to wait without timeouts in testWaitingConsumer and
testTransfer2.

This is a temporary change for a debugging purpose and to be reverted.
This shouldn't affect the effectiveness of the tests because the test
code assumes timeouts mean test failures.

Bug: 25883050
Bug: 12687968
Change-Id: Iffd0377de5a416a308233e8b3cc345a83bdc406a
8e9a0e92906742b17eb08d7fb83cca91965f9b8e 28-Apr-2015 Narayan Kamath <narayan@google.com> Update JSR166 tck tests.

The following tests have been omitted because they are
unsupported :

- Atomic8Test.java
- CompletableFutureTest.java
- ConcurrentHashMap8Test.java
- DoubleAccumulatorTest.java
- DoubleAdderTest.java
- ForkJoinPool8Test.java
- ForkJoinTask8Test.java
- LongAccumulatorTest.java
- LongAdderTest.java
- SplittableRandomTest.java
- StampedLockTest.java
- ThreadLocalRandom8Test.java
- ThreadPoolExecutor9Test.java

A package declaration has been added to all files (package jsr166;)
and the base-class JSR166Test has been changed not to rely on features
that aren't available on android / junit in the android environment.

We also avoid using junit4 style TestSuite declarations. While the CTS
test runner handles them properly usually, it trips over itself when it
encounters a failure and tries to run each test in an invidual process
and fails each test for no good reason (needs investigation on the CTS
side of things)

bug: 20628776

(cherry picked from commit 5da8b2b3cac51f0f592a5e1941bd84eade9648cd)

Change-Id: If35be0881ad8da4c604ce6683149b15c1a85f289
5da8b2b3cac51f0f592a5e1941bd84eade9648cd 28-Apr-2015 Narayan Kamath <narayan@google.com> Update JSR166 tck tests.

The following tests have been omitted because they are
unsupported :

- Atomic8Test.java
- CompletableFutureTest.java
- ConcurrentHashMap8Test.java
- DoubleAccumulatorTest.java
- DoubleAdderTest.java
- ForkJoinPool8Test.java
- ForkJoinTask8Test.java
- LongAccumulatorTest.java
- LongAdderTest.java
- SplittableRandomTest.java
- StampedLockTest.java
- ThreadLocalRandom8Test.java
- ThreadPoolExecutor9Test.java

A package declaration has been added to all files (package jsr166;)
and the base-class JSR166Test has been changed not to rely on features
that aren't available on android / junit in the android environment.

We also avoid using junit4 style TestSuite declarations. While the CTS
test runner handles them properly usually, it trips over itself when it
encounters a failure and tries to run each test in an invidual process
and fails each test for no good reason (needs investigation on the CTS
side of things)

bug: 20628776

Change-Id: Iddccfe89d5faac3249ebd8976145ef95f63a1186
008167dfe7530e6a80066006633f2301d3eae012 15-May-2014 Calin Juravle <calin@google.com> Fix jsr166 tests

Tests specified as static inner classes were failing because the CTS
runner does not support them. The temporary fix is to promote all static
inner test classes to top level classes. This should be reverted once
the CTS runner is fixed.

Bug: 13877168
Change-Id: Icb64d7d7fcf6202d54d6fe31d9e1c9a6a43a233b
8f0d92bba199d906c70a5e40d7f3516c1a424117 01-Aug-2013 Calin Juravle <calin@google.com> Added jsr166 tck tests as part of the libcore testsuite.

Change-Id: I6094d734f818fa043f2b277cf2b4ec7fec68e26e