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

P4 plugin tests fail when run on a Windows machine

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: p4-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      The following p4-plugin tests fail when run on my Windows machine:

      • JenkinsfileTest
        • testDiffClients
        • testMultiSyncPolling
        • testMultiSyncParallelPolling
        • testBasicJenkinsfile
      • PollingTest
        • testPollingMaskExcl
        • testPollingInc
        • testPollingPi
        • testPatternListCaseSensitive
        • shouldTriggerJobifChanges
        • testPatternListInvalidPattern
        • testPatternList
      • WorkflowTest
        • testWorkflowEnv
      • PerforceScmSourceTest
        • testStarPathClassic
        • testMultiBranchClassicWithCredentialsInFolder
        • testRootPathClassic
        • testMultiPathWithClassic
        • testMultiBranchWithClassic

       

      After investigation I've determined that the JenkinsfileTest, PollingTest, and WorkflowTest tests are failing due to performance issus, and the PerforceScmSourceTest tests are failing due to a problem with the way the Java path object converts to Windows paths.

        Attachments

          Activity

          Hide
          msmeeth Matthew Smeeth added a comment -
          Show
          msmeeth Matthew Smeeth added a comment - Fixed in: JENKINS-52145-Updated tests to work against Windows, and lower spec computers    #74 by  msmeeth56  was merged 4 days ago    

            People

            Assignee:
            p4paul Paul Allen
            Reporter:
            msmeeth Matthew Smeeth
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: