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

Publisher creates files with names that are too long to read and fails

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: nunit-plugin
    • Labels:
      None
    • Environment:
      Windows Server 2012 R2
      Jenkins 2.46.2
      Pipeline plugin 2.5
      nunit 3.6
      nunit-plugin 0.20
    • Similar Issues:

      Description

      Tests with long namespace names and multiple cases cause the publisher to create intermediate files whose names are 260-character long. In Windows 2012 R2 they become inaccessible, so the publisher fails.

       

      Attached is a sample output xml from nunit that causes the publisher to generate files with names that are too long to be accessible.

        Attachments

          Activity

          Hide
          slide_o_mix Alex Earl added a comment -

          No, they use their own NUnit translation. They don't depend on the NUnit plugin to do the translation from NUnit to JUnit.

          Show
          slide_o_mix Alex Earl added a comment - No, they use their own NUnit translation. They don't depend on the NUnit plugin to do the translation from NUnit to JUnit.
          Hide
          teognost Adi Adrian added a comment -

          The error above appeared when I publish the results through Xunit plugin and choosing NUnit.When I use directly the Nunit plugin -Publish Nunit Test results report -it works ok.I suppose you cannot do anything to fix this plugin https://wiki.jenkins.io/display/JENKINS/xUnit+Plugin?

          Show
          teognost Adi Adrian added a comment - The error above appeared when I publish the results through Xunit plugin and choosing NUnit.When I use directly the Nunit plugin -Publish Nunit Test results report -it works ok.I suppose you cannot do anything to fix this plugin https://wiki.jenkins.io/display/JENKINS/xUnit+Plugin?
          Hide
          teognost Adi Adrian added a comment -

          I installed now the 0.21 version of the NUnit plugin and tested it with the attached TestResults4.xml.It failed like before with 0.20 version of the Nunit plugin:
          10:53:39 Run condition [Current build status] enabling perform for step [[Publish xUnit test result report]]10:53:39 [xUnit] [INFO] - Starting to record.10:53:39 [xUnit] [INFO] - Processing NUnit-Version N/A (default)10:53:39 [xUnit] [INFO] - [NUnit-Version N/A (default)] - 1 test report file(s) were found with the pattern 'UT/.xml' relative to 'C:\Program Files (x86)\Jenkins\jobs\Publish Nunit Results1\workspace' for the testing framework 'NUnit-Version N/A (default)'.*10:53:39 [xUnit] [ERROR] - The converted file for the result file 'C:\Program Files (x86)\Jenkins\jobs\Publish Nunit Results1\workspace\UT\TestResults4.xml' (during conversion process for the metric 'NUnit') is not valid. The report file has been skipped.10:53:39 [xUnit] [ERROR] - Content is not allowed in prolog.10:53:39 [xUnit] [ERROR] - Content is not allowed in prolog.10:53:39 [xUnit] [ERROR] - There is at least one problem. Check the Jenkins system log for more information. (if you don't have configured yet the system log before, you have to rebuild).10:53:40 [xUnit] [ERROR] - The plugin hasn't been performed correctly: Problem on deletion*10:53:40* Build step 'Flexible publish' changed build result to FAILURE

          Show
          teognost Adi Adrian added a comment - I installed now the 0.21 version of the NUnit plugin and tested it with the attached TestResults4.xml.It failed like before with 0.20 version of the Nunit plugin: 10:53:39 Run condition [Current build status] enabling perform for step [ [Publish xUnit test result report] ] 10:53:39 [xUnit] [INFO] - Starting to record. 10:53:39 [xUnit] [INFO] - Processing NUnit-Version N/A (default) 10:53:39 [xUnit] [INFO] - [NUnit-Version N/A (default)] - 1 test report file(s) were found with the pattern 'UT/ .xml' relative to 'C:\Program Files (x86)\Jenkins\jobs\Publish Nunit Results1\workspace' for the testing framework 'NUnit-Version N/A (default)'.*10:53:39 [xUnit] [ERROR] - The converted file for the result file 'C:\Program Files (x86)\Jenkins\jobs\Publish Nunit Results1\workspace\UT\TestResults4.xml' (during conversion process for the metric 'NUnit') is not valid. The report file has been skipped. 10:53:39 [xUnit] [ERROR] - Content is not allowed in prolog. 10:53:39 [xUnit] [ERROR] - Content is not allowed in prolog. 10:53:39 [xUnit] [ERROR] - There is at least one problem. Check the Jenkins system log for more information. (if you don't have configured yet the system log before, you have to rebuild). 10:53:40 [xUnit] [ERROR] - The plugin hasn't been performed correctly: Problem on deletion*10:53:40* Build step 'Flexible publish' changed build result to FAILURE
          Hide
          towel Yoav Miles added a comment -

          Adi, what I did in the mean time was to generate nunit v2 results, which don't seem to cause this effect.

          Show
          towel Yoav Miles added a comment - Adi, what I did in the mean time was to generate nunit v2 results, which don't seem to cause this effect.
          Hide
          teognost Adi Adrian added a comment -

          Thanks!When it will be released 0.21?

          Show
          teognost Adi Adrian added a comment - Thanks!When it will be released 0.21?

            People

            • Assignee:
              slide_o_mix Alex Earl
              Reporter:
              towel Yoav Miles
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: