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

'Run could not start' error from HPE Application Automation Tools plugin

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • Jenkins V2.121.1, Micro Focus Application Automation Tools 5.4.3-beta-SNAPSHOT (private-a0427562-dananda) Performance Center 12.56

      Following on from JENKINS-52366, the version of the automation tools plugin from that bug has an issue when running a build job. This is the Jenkins log;

      Fri 07.20.2018 at 11:21:44 AM BST - 
      Run started (TestID: 1764, RunID: 1905, TimeslotID: 4001)

      Fri 07.20.2018 at 11:21:48 AM BST - Error: executeRequest exception: Operation failed. Error code: 1001
      Fri 07.20.2018 at 11:21:48 AM BST - Error: Run could not start!
      Fri 07.20.2018 at 11:21:49 AM BST - Logout succeeded
      Fri 07.20.2018 at 11:21:49 AM BST - Empty Results
      Fri 07.20.2018 at 11:21:49 AM BST - Result Status (PC RunID: 1905): FAILURE

       

      Checking the corresponding test in Performance Center showed that it was triggered correctly, the test continues to run and passes successfully. The run information from Performance Center shows the following;

       

      Test Name hello_world
      Run ID 1905
      End time 07/20/2018 11:22:02

       

      This was broken during the fix for 52366, I was able to run a successful job on the 17th of July but it had stopped working by the 20th. The bug log suggest the change for DecimalFormatSymbols whitelisting broke the build job. 

            danieldanan Daniel Danan
            simon_norris Simon Norris
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: