: Re: Jenkins bug JENKINS-12235 - suggestions please
You might want to try anything from 1.533 onwards... I'm not saying the issue
is fixed... just that those versions are at least not hiding the next link in
the chain towards the root cause.
On 24 January 2014 14:06, David Al
i-users@googlegroups.com] *On Behalf Of *Stephen Connolly
> *Sent:* 24 January 2014 14:01
>
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: Jenkins bug JENKINS-12235 - suggestions please
>
>
>
> From the stack trace, you are likely running on a version of Jenkins t
Stephen Connolly
Sent: 24 January 2014 14:01
To: jenkinsci-users@googlegroups.com
Subject: Re: Jenkins bug JENKINS-12235 - suggestions please
>From the stack trace, you are likely running on a version of Jenkins that does
>not include the extra diagnostics against JENKINS-5073 (most likely th
>From the stack trace, you are likely running on a version of Jenkins that
does not include the extra diagnostics against JENKINS-5073 (most likely
the root cause) which were added in this commit:
https://github.com/jenkinsci/jenkins/commit/1b22559581abf87344c57ac0dcf21d1612f2c80b
So the real caus
Sent: 24 January 2014 13:47
To: jenkinsci-users@googlegroups.com
Subject: Re: Jenkins bug JENKINS-12235 - suggestions please
>From what I can see from the discussion, it sounds like the windows forked
>process gets "picked up" as terminated if it is not sending output back t
>From what I can see from the discussion, it sounds like the windows forked
process gets "picked up" as terminated if it is not sending output back to
the Jenkins slave process at a regular pace... if that were to happen, the
Jenkins slave process would assume that the script used to execute the
sc
Hi
One of our users writes:
Bug https://issues.jenkins-ci.org/browse/JENKINS-12235 is now seriously
hampering our uptake of Jenkins. Our builds are very unreliable, to the point
where we can't really use Jenkins for any critical regression testing or
compilations because they too often fail to
