Pax Drone
  1. Pax Drone
  2. PAXDRONE-24

Test fails with non responding framework while prior tests ran successfully

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.1.1
    • Fix Version/s: 0.1.2
    • Component/s: None
    • Labels:
      None

      Description

      This is most probably bug. I'm not sure why this happened. After I
      killed the process and re-run the test manually on srv03.
      I get this error.

      -------------------------------------------------------------------------------
      Test set: org.ops4j.pax.wicket.it.lifecycle.tracker.WicketApplicationTrackTest
      -------------------------------------------------------------------------------
      Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 33.975
      sec <<< FAILURE!
      testApplicationTracker(org.ops4j.pax.wicket.it.lifecycle.tracker.WicketApplicationTrackTest)
      Time elapsed: 33.32 sec <<< ERROR!
      java.lang.RuntimeException: NOT RESPONDING! Last exception:
      at org.ops4j.pax.drone.connector.paxrunner.intern.PaxRunnerInstanceImpl$Runner.executeProcess(PaxRunnerInstanceImpl.java:164)
      at org.ops4j.pax.drone.connector.paxrunner.intern.PaxRunnerInstanceImpl$Runner.exec(PaxRunnerInstanceImpl.java:121)
      at org.ops4j.pax.runner.platform.internal.PlatformImpl.start(PlatformImpl.java:243)
      at org.ops4j.pax.runner.Run.startPlatform(Run.java:429)
      at org.ops4j.pax.runner.Run.start(Run.java:157)
      at org.ops4j.pax.drone.connector.paxrunner.intern.PaxRunnerInstanceImpl.startup(PaxRunnerInstanceImpl.java:74)
      at org.ops4j.pax.drone.connector.paxrunner.intern.PaxRunnerConnector.execute(PaxRunnerConnector.java:57)

      Note: This is the 3rd test. The first two passed succesfully.

        Activity

        Hide
        Toni Menzel added a comment -

        The reason should be that the forked process didn't shutdown fast enough for the last test to run.
        With the latest changes (for PAXDRONE-23) this behaviour has been observed (a test picked 1099, then 1100, then 1099 and 1100 again).
        With that, the problem should not be a real problem anymore. (it picks the next free port).

        Show
        Toni Menzel added a comment - The reason should be that the forked process didn't shutdown fast enough for the last test to run. With the latest changes (for PAXDRONE-23 ) this behaviour has been observed (a test picked 1099, then 1100, then 1099 and 1100 again). With that, the problem should not be a real problem anymore. (it picks the next free port).

          People

          • Assignee:
            Toni Menzel
            Reporter:
            Edward Yakop
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development