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

XML parser crash

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: xunit-plugin
    • Labels:
      None
    • Environment:
      Windows Server 2016, Weekly jenkins, running as service
    • Similar Issues:

      Description

      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
      

        Attachments

          Activity

          Hide
          nfalco 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.
          Show
          nfalco 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.
          Hide
          arbeita 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.

          Show
          arbeita 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.
          Hide
          nfalco 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?

          Show
          nfalco 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?
          Hide
          arbeita 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.

          Show
          arbeita 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.
          Hide
          nfalco Nikolas Falco added a comment -

          ok, Now I understand where the versions comes.

          May I have the crash log of the thread dump log? Otherwise I have idea where looking for this issue

           

          Show
          nfalco Nikolas Falco added a comment - ok, Now I understand where the versions comes. May I have the crash log of the thread dump log? Otherwise I have idea where looking for this issue  
          Hide
          arbeita Ronny Borchert added a comment -

          Since the jenkins is killing itself. I cannot provide such dump.

          Show
          arbeita Ronny Borchert added a comment - Since the jenkins is killing itself. I cannot provide such dump.
          Hide
          arbeita Ronny Borchert added a comment -

          Today we had a stucking unit test. We have jobs with child jobs. The Xunit is in the child job. So I stopped the main job, but it look like the child job didn't. So I clicked on kill the child job too. Then it appears that jenkins was dead. Not sure if by killing main job or child job. No error in jenkins log file. In error log I see:

           

          Child process [3988 - H:\Jenkins\jre\bin\java -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort=yyy -Xrs -Xmx512m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "H:\Jenkins\jenkins.war" --httpPort=8080] finished with -1073741510

           

          The error code is in hex: 0xC000013A

           

          So I guess 13A is 314 and from this page https://docs.microsoft.com/de-de/windows/win32/debug/system-error-codes--0-499-

          it is:

           

          ERROR_DISK_RESOURCES_EXHAUSTED

          314 (0x13A)

          The physical resources of this disk have been exhausted.

           

           

           

          Show
          arbeita Ronny Borchert added a comment - Today we had a stucking unit test. We have jobs with child jobs. The Xunit is in the child job. So I stopped the main job, but it look like the child job didn't. So I clicked on kill the child job too. Then it appears that jenkins was dead. Not sure if by killing main job or child job. No error in jenkins log file. In error log I see:   Child process [3988 - H:\Jenkins\jre\bin\java -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort=yyy -Xrs -Xmx512m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "H:\Jenkins\jenkins.war" --httpPort=8080] finished with -1073741510   The error code is in hex: 0xC000013A   So I guess 13A is 314 and from this page  https://docs.microsoft.com/de-de/windows/win32/debug/system-error-codes--0-499- it is:   ERROR_DISK_RESOURCES_EXHAUSTED 314 (0x13A) The physical resources of this disk have been exhausted.      
          Hide
          arbeita Ronny Borchert added a comment -

          java_mini.dmp

          I attached me with visual studio then I killed the job with xUnit. The exception was raised and I created a dump. Please find it attached.

          Show
          arbeita Ronny Borchert added a comment - java_mini.dmp I attached me with visual studio then I killed the job with xUnit. The exception was raised and I created a dump. Please find it attached.

            People

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

              Dates

              Created:
              Updated: