| 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. |