On 20/03/2015 00:12, Joseph D. Darcy wrote:
Hello,
Per recent proposals
(http://mail.openjdk.java.net/pipermail/jdk9-dev/2015-March/001991.html),
please review the change below for
JDK-8075565: Define @intermittent jtreg keyword and mark
intermittently failuring jdk tests
http://cr.openjdk.java.net/~darcy/8075565.0/
which defines an "intermittent" keyword for use in jtreg tests and
then marks the initial rouges gallery of known or suspected
intermittently failing tests:
test/com/sun/jndi/ldap/LdapTimeoutTest.java
test/java/lang/invoke/MethodHandles/CatchExceptionTest.java
test/java/lang/ref/OOMEInReferenceHandler.java
test/java/net/Inet6Address/serialize/Inet6AddressSerializationTest.java
test/java/net/SocketPermission/SocketPermissionTest.java
test/java/nio/channels/AsynchronousSocketChannel/Basic.java
test/java/nio/channels/Selector/Wakeup.java
test/java/nio/channels/ServerSocketChannel/AdaptServerSocket.java
test/java/nio/channels/spi/SelectorProvider/inheritedChannel/run_tests.sh
test/java/nio/file/FileStore/Basic.java
test/java/nio/file/Files/InterruptCopy.java
test/java/rmi/activation/Activatable/checkActivateRef/CheckActivateRef.java
test/java/rmi/registry/interfaceHash/InterfaceHash.java
test/java/rmi/server/UnicastRemoteObject/exportObject/GcDuringExport.java
I compiled the list by going through open test-related bugs in
core-libs components and a few other components. I'll send a follow-up
message to security-libs to get their sets marked. I generally tried
to only mark tests as intermittent if there was recent (six months old
or new) information about a failure. Therefore, this initial list is
not comprehensive and tests should have the keyword added as they are
observed to intermittently fail. Also, tests should have the keyword
removed if they are corrected to address the cause of the intermittent
failure!
I verified
jtreg -l -k:intermittent
selects the right number of tests.
Full patch below.
Please hold on on this until folks get a chance to look at the reasons
why the tests are getting this keyword. In at least some cases then the
issues aren't test issues but infrastructure issues.
-Alan
