Version 8

    A flaky test is a test which does not give a reliable pass fail result. For example, if we had a test which, under the same architecture-OS-JVM combination, returns pass sometimes and fail other times, then this test is flaky. Tests can be flaky if they directly involve some form of non-determinism, and the non-determinsism is affecting the result. Tests can also appear to be flaky if they depend upon a component which is itself flaky. For example, if your test depended on the correct deployment of certain resources, and the deployment of the resources was flaky (does not reliably occur), then the test may appear to be flaky.

     

    The aim of this page is to provide a place to record tests which we have found to be flaky, so that they may later be investigated and made deterministic. Please list the architcure, OS and JVM combination used to run the test.

     

    test package name (prefixed by org.jboss.test)

    test name

    AS release

    arch

    os

    jvm

    description

    deployers.jbas2904.test.EARDeploymentUnitTestCase

    testEARDeployment

    4.2.0

    x86

    W2K3

    Sun

    repeatedly passes and fails

    cmp2.optimisticlock.test.OptimisticLockUnitTestCase

    testTimestampStrategyFail

    4.2.0

    x86

    W2K3

    Sun

    repeatedly passes and fails

    timer.test.BasicTimerUnitTestCase

    testMDBTimer

    4.2.0

    x86,x86_64

    W2K3

    Sun,BEA

    repeatedly passes and fails, see JBAS-3738

    pooled.test.SSLSocketsUnitTestCase

    testClientCertSSLAccess

    4.2.0

    x86,x86_64

    W2K3

    Sun,BEA

    repeatedly passes and fails

    jbossmq.test.SecurityUnitTestCase

    runLoginTest

    4.2.0

    x86

    W2K3

    Sun

    repeatedly passes and fails, seeJBAS-3739