[JIRA] (JENKINS-55796) Random "process apparently never started" error

[vincent@massol.net (JIRA)]

Vincent Massol created an issue

Jenkins / JENKINS-55796 Random "process apparently never started" error Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2019-01-27 10:27 Environment: Jenkins 2.150.2 Pipeline Maven plugin 3.6.7 Priority: Minor Reporter: Vincent Massol Just got this on XWiki's CI: https://ci.xwiki.org/blue/organizations/jenkins/XWiki%2Fxwiki-platform/detail/master/1403/pipeline INFO] --- maven-surefire-plugin:2.22.0:test (default-test) @ xwiki-platform-image-plugin --- [INFO] Surefire report directory: /home/hudsonagent/jenkins_root/workspace/XWiki_xwiki-platform_master-ZGNMAWOYB6APYNMYWF7HH475RM4M6C6RE2U76Y5M5RWNQJWOLFGA/xwiki-platform-core/xwiki-platform-image/xwiki-platform-image-plugin/target/surefire-reports [INFO] [INFO] ------------------------------------------------------- [INFO] T E S T S [INFO] ------------------------------------------------------- [INFO] Running com.xpn.xwiki.plugin.image.ImagePluginTest process apparently never started in /home/hudsonagent/jenkins_root/workspace/XWiki_xwiki-platform_master-ZGNMAWOYB6APYNMYWF7HH475RM4M6C6RE2U76Y5M5RWNQJWOLFGA@tmp/durable-41a561b2 sh: 1: cannot create /home/hudsonagent/jenkins_root/workspace/XWiki_xwiki-platform_master-ZGNMAWOYB6APYNMYWF7HH475RM4M6C6RE2U76Y5M5RWNQJWOLFGA@tmp/durable-41a561b2/jenkins-result.txt.tmp: Directory nonexistent mv: cannot stat `/home/hudsonagent/jenkins_root/workspace/XWiki_xwiki-platform_master-ZGNMAWOYB6APYNMYWF7HH475RM4M6C6RE2U76Y5M5RWNQJWOLFGA@tmp/durable-41a561b2/jenkins-result.txt.tmp': No such file or directory script returned exit code -2 Any idea what could be the cause? Thanks Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[kivagant@gmail.com (JIRA)]

Eugene G commented on JENKINS-55796

Re: Random "process apparently never started" error I'm not sure if my case somehow linked to the case from the ticket but for those who will be looking for similar problems: in my case it was caused by dead sidecar docker container: docker.image('elasticsearch:6.4.0').withRun() { es -> image.inside("--link ${es.id}:es") { sh 'my_script.sh' // process apparently never started in ... } } So Elasticsearch image started and exited with an error but Jenkins doesn't control this, so I got the problem.

Add Comment