[JIRA] (JENKINS-60240) XML parser crash

21 views
Skip to first unread message

nfalco79@hotmail.com (JIRA)

unread,
Jan 12, 2020, 9:48:02 AM1/12/20
to jenkinsc...@googlegroups.com
Nikolas Falco updated an issue
 
Jenkins / Bug JENKINS-60240
XML parser crash
Change By: Nikolas Falco
Summary: crash XML parser crash
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

ronny.borchert@muehlbauer.de (JIRA)

unread,
Jan 13, 2020, 12:27:02 AM1/13/20
to jenkinsc...@googlegroups.com
Ronny Borchert updated an issue
Change By: Ronny Borchert
Environment: Windows Server 2016, Weekly jenkins , running as service

ronny.borchert@muehlbauer.de (JIRA)

unread,
Jan 13, 2020, 12:27:03 AM1/13/20
to jenkinsc...@googlegroups.com
Ronny Borchert updated an issue
Change By: Ronny Borchert
Environment: latest Windows Server 2016, Weekly jenkins

ronny.borchert@muehlbauer.de (JIRA)

unread,
Jan 13, 2020, 12:29:04 AM1/13/20
to jenkinsc...@googlegroups.com
Ronny Borchert commented on Bug JENKINS-60240
 
Re: XML parser crash

I am not sure how it comes to this version number, 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.

ronny.borchert@muehlbauer.de (JIRA)

unread,
Jan 13, 2020, 12:32:02 AM1/13/20
to jenkinsc...@googlegroups.com
Ronny Borchert edited a comment on Bug JENKINS-60240
 
Re: XML parser crash
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.

nfalco79@hotmail.com (JIRA)

unread,
Feb 9, 2020, 10:10:03 AM2/9/20
to jenkinsc...@googlegroups.com
Nikolas Falco commented on Bug JENKINS-60240
 
Re: XML parser crash

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@muehlbauer.de (JIRA)

unread,
Feb 10, 2020, 1:55:02 AM2/10/20
to jenkinsc...@googlegroups.com
Ronny Borchert updated an issue
Change By: Ronny Borchert
Attachment: plugin config.png

ronny.borchert@muehlbauer.de (JIRA)

unread,
Feb 10, 2020, 1:57:04 AM2/10/20
to jenkinsc...@googlegroups.com
Ronny Borchert commented on Bug JENKINS-60240
 
Re: XML parser crash

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

nfalco79@hotmail.com (JIRA)

unread,
Feb 10, 2020, 6:03:02 AM2/10/20
to jenkinsc...@googlegroups.com
Nikolas Falco commented on Bug JENKINS-60240
 
Re: XML parser crash

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

 

ronny.borchert@muehlbauer.de (JIRA)

unread,
Feb 10, 2020, 6:08:03 AM2/10/20
to jenkinsc...@googlegroups.com
Ronny Borchert commented on Bug JENKINS-60240
 
Re: XML parser crash

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

ronny.borchert@muehlbauer.de (JIRA)

unread,
Feb 26, 2020, 1:38:02 AM2/26/20
to jenkinsc...@googlegroups.com
 
Re: XML parser crash

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.

 

 

 

ronny.borchert@muehlbauer.de (JIRA)

unread,
Mar 5, 2020, 12:43:02 AM3/5/20
to jenkinsc...@googlegroups.com
Ronny Borchert updated an issue
Change By: Ronny Borchert
Attachment: java_mini.dmp
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

ronny.borchert@muehlbauer.de (JIRA)

unread,
Mar 5, 2020, 12:44:02 AM3/5/20
to jenkinsc...@googlegroups.com
 
Re: XML parser crash

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.

Reply all
Reply to author
Forward
0 new messages