Some erratic errors started to happen as a consequence of https://issues.jenkins-ci.org/browse/JENKINS-58290 

[2019-09-30T15:00:13.698Z] process apparently never started in /var/lib/jenkins/workspace/ejs_apm-agent-nodejs-mbp_PR-1393@tmp/durable-3a70569b
[2019-09-30T15:00:13.698Z] (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
script returned exit code -2  

Unfortunately, it seems the error to fail, for some reason, just in one particular PR rather than been affecting the whole CI!

- https://github.com/elastic/apm-agent-nodejs/pull/1393

Apparently it happens when running a docker inside of a worker.

Besides, I'd expect the behavior of using LAUNCH_DIAGNOSTICS as the default one for backward compatibilities rather than the other way around

Please let me know if you need further details, my only and big concern is what the heck happens to only being failing in one particular PR of an MBP rather than in all of them... that's really weird.