• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • xunit-plugin
    • None
    • Windows Server 2016, Weekly jenkins, running as service

      We tried today to cancel a unit test then jenkins crashed with error. Unit test is xUnit Cpp1.12.1 plugin.

      2019-11-21 11:36:46.158+0000 [id=5247] INFO hudson.model.Run#execute: xxx_RunUnitTest #60 main build action completed: SUCCESS
      2019-11-21 11:36:46.158+0000 [id=5247] INFO hudson.model.Run#execute: SRPFwk_Dev_RunUnitTest #60 main build action completed: SUCCESS
      Recoverable error on line 2 column 9   SXXP0003: Error reported by XML parser: Document is invalid: no grammar found.
      Recoverable error on line 2 column 9   SXXP0003: Error reported by XML parser: Document root element "TestRun", must match  DOCTYPE root "null".
      Warning   The XML parser reported two validation errors. Processing continues, because recovery from  validation errors was requested
      

          [JENKINS-60240] XML parser crash

          Ronny Borchert created issue -
          Nikolas Falco made changes -
          Description Original: We tried today to cancel a unit test then jenkins crashed with error. Unit test is xUnit Cpp1.12.1 plugin.

           

          2019-11-21 11:36:46.158+0000 [id=5247] INFO hudson.model.Run#execute: xxx_RunUnitTest #60 main build action completed: SUCCESS2019-11-21 11:36:46.158+0000 [id=5247] INFO hudson.model.Run#execute: SRPFwk_Dev_RunUnitTest #60 main build action completed: SUCCESSRecoverable error on line 2 column 9   SXXP0003: Error reported by XML parser: Document is invalid: no grammar found.Recoverable error on line 2 column 9   SXXP0003: Error reported by XML parser: Document root element "TestRun", must match  DOCTYPE root "null".Warning   The XML parser reported two validation errors. Processing continues, because recovery from  validation errors was requested
          New: We tried today to cancel a unit test then jenkins crashed with error. Unit test is xUnit Cpp1.12.1 plugin.
          {noformat}
          2019-11-21 11:36:46.158+0000 [id=5247] INFO hudson.model.Run#execute: xxx_RunUnitTest #60 main build action completed: SUCCESS
          2019-11-21 11:36:46.158+0000 [id=5247] INFO hudson.model.Run#execute: SRPFwk_Dev_RunUnitTest #60 main build action completed: SUCCESS
          Recoverable error on line 2 column 9   SXXP0003: Error reported by XML parser: Document is invalid: no grammar found.
          Recoverable error on line 2 column 9   SXXP0003: Error reported by XML parser: Document root element "TestRun", must match  DOCTYPE root "null".
          Warning   The XML parser reported two validation errors. Processing continues, because recovery from  validation errors was requested
          {noformat}

          Nikolas Falco added a comment - - edited

          In logs you had post I can not see any blocking error. I can see only warning and info logs.

          Need more (moooooore) informations like:

          • which plugin version are you using? (xUnit Cpp1.12.1 plugin is unknown)
          • which environment, which jenkins version?
          • attaching the test report source file maybe could help a bit. Which configuration.

          Nikolas Falco added a comment - - edited In logs you had post I can not see any blocking error. I can see only warning and info logs. Need more (moooooore) informations like: which plugin version are you using? (xUnit Cpp1.12.1 plugin is unknown) which environment, which jenkins version? attaching the test report source file maybe could help a bit. Which configuration.
          Nikolas Falco made changes -
          Summary Original: crash XML parser crash New: XML parser crash
          Ronny Borchert made changes -
          Environment Original: latest New: Windows Server 2016, Weekly jenkins
          Ronny Borchert made changes -
          Environment Original: Windows Server 2016, Weekly jenkins New: Windows Server 2016, Weekly jenkins, running as service

          Ronny Borchert added a comment - - edited

          I am not sure how it comes to this version number mix up, we used the latest from all plugins. At time of the plugin bug report creation it was XUnit in version 2.3.6.

          We use the weekly version and update nearly every week. In logs I see error caused by empty XUnit result file. I guess this lead to crash. The empty files got created by a crashing or canceled test run.

          edit:

          1.12.1 is the version of th Cpp Report Type used by the XUnit plugin, I am not sure if this is something predefined or created by colleague.

          Ronny Borchert added a comment - - edited I am not sure how it comes to this version number mix up, we used the latest from all plugins. At time of the plugin bug report creation it was XUnit in version 2.3.6. We use the weekly version and update nearly every week. In logs I see error caused by empty XUnit result file. I guess this lead to crash. The empty files got created by a crashing or canceled test run. edit: 1.12.1 is the version of th Cpp Report Type used by the XUnit plugin, I am not sure if this is something predefined or created by colleague.

          Nikolas Falco added a comment -

          I still don't understand which ones a bug was opened on since there are no crashes from the only log.

          Also I don't understand the version of the CPP Report Type what it refers to. Is it a plugin that you have installed in jenkins? Is this the version of the tool you use to generate test reports? What does that version 1.21.1 represent?

          Nikolas Falco added a comment - I still don't understand which ones a bug was opened on since there are no crashes from the only log. Also I don't understand the version of the CPP Report Type what it refers to. Is it a plugin that you have installed in jenkins? Is this the version of the tool you use to generate test reports? What does that version 1.21.1 represent?
          Ronny Borchert made changes -
          Attachment New: plugin config.png [ 50168 ]

          I attached the configuration screen. Since it is labled as default in combo box, I believe it comes from plugin itself.

          Ronny Borchert added a comment - I attached the configuration screen. Since it is labled as default in combo box, I believe it comes from plugin itself.

            nfalco Nikolas Falco
            arbeita Ronny Borchert
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: