Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12377

Jenkins fitnesse build aborts after HTTP Timeout is exceeded, but tests continue to run

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: fitnesse-plugin
    • Labels:
      None
    • Environment:
      Jenkins ver. 1.446
      Hudson Fitnesse plugin 1.4
    • Similar Issues:

      Description

      To reproduce:
      1. Start Fitnesse on a target machine
      2. Setup a Jenkins job to build using the 'Fitnesse instance is already running' option
      3. Set the 'HTTP Timeout (ms)' to a value which will cause the test to timeout

      Result:
      > Jenkins build is classed as Aborted when the timeout value is exceeded, however the Fitnesse tests on the target machine continue to run

      Expected Result:
      > Jenkins build failing or aborting should force Fitnesse for stop tests

        Attachments

          Activity

          Hide
          mguine01 Mike Guiney added a comment -

          Hi,
          I'm seeing very similar behaviour. I would have expected the FitServer.exe process to eventually finish but I guess its hung for some reason (hence the timeout). Trying to debug now. I'm also using a combination of timeouts i.e. the Http timeout thats part of the fitnesse plugin and a Build Timeout plugin for the job. More testing required I guess...
          Mike

          Show
          mguine01 Mike Guiney added a comment - Hi, I'm seeing very similar behaviour. I would have expected the FitServer.exe process to eventually finish but I guess its hung for some reason (hence the timeout). Trying to debug now. I'm also using a combination of timeouts i.e. the Http timeout thats part of the fitnesse plugin and a Build Timeout plugin for the job. More testing required I guess... Mike
          Hide
          mguine01 Mike Guiney added a comment -

          Hi,
          A closer look at this seems to be an issue with the fitnesse instance not handling multiple clients running custom suites in parallel. We use custom tags in fitnesse to run a subset of tests as part of a number of smoke test jobs. Our Fitnesse instance doesn't respond well to FitServer.exe which is left hanging in the wind. still investigating...
          Mike

          Show
          mguine01 Mike Guiney added a comment - Hi, A closer look at this seems to be an issue with the fitnesse instance not handling multiple clients running custom suites in parallel. We use custom tags in fitnesse to run a subset of tests as part of a number of smoke test jobs. Our Fitnesse instance doesn't respond well to FitServer.exe which is left hanging in the wind. still investigating... Mike
          Hide
          td tsd 123 added a comment -

          Hi,
          I am using fitnesse plugin and facing this issue. Can i expect any updates on this JIRA?

          Regards,
          T

          Show
          td tsd 123 added a comment - Hi, I am using fitnesse plugin and facing this issue. Can i expect any updates on this JIRA? Regards, T

            People

            • Assignee:
              Unassigned
              Reporter:
              ashokm Ashok Manji
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: