Uploaded image for project: 'CDI TCK'
  1. CDI TCK
  2. CDITCK-368

InterceptorInvocationTest possibly unstable

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.1.1.Final, 1.2.0.Beta1
    • None
    • None
    • None

      org.jboss.cdi.tck.tests.interceptors.invocation.InterceptorInvocationTest.testTimeoutMethodIntercepted() may fail as the timeout notification is delivered after the TCK's timer times out. Although very unlikely, I've seen this happen several times e.g. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Weld/view/Weld%202%20CI/job/Weld-2.x-pull-player-executor/123/console

      I suggest to increase the timeout period (1s currently) to e.g. 10s and change the stop condition to

      Timing.timeoutAt != null
      

      in https://github.com/cdi-spec/cdi-tck/blob/master/impl/src/main/java/org/jboss/cdi/tck/tests/interceptors/invocation/InterceptorInvocationTest.java#L161
      for the test to execute quickly if everything works as expected yet being tolerant to timing issues and slow machines.

              mkouba@redhat.com Martin Kouba
              rhn-engineering-jharting Jozef Hartinger
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: