Re: [ee4j-build] Unexpected Jenkins failure with "git checkout" returnin

[Stuart Douglas <sdouglas@xxxxxxxxxx>]

We have actually been seeing this same issue intermittently in the Quarkus CI over the last few days, with our azure pipelines jobs failing on checkout with 137. I have never seen this before, so it is odd that two completely unrelated projects with completely different setups hit it in the same week.

The only commonality here seems to be github, but I have no idea what the problem could be.

Stuart

On Fri, 17 Jan 2020 at 14:23, Scott Marlow <smarlow@xxxxxxxxxx> wrote:

Hi,

Any insight as to what this failure [1] represents and how to resolve?
 The command being executed is "git checkout -f
c457c40af61d307b0dea0e0489fed7ab4c3e8490" and the exit code is 137,
which could mean a memory allocation issue (from googling for that
exit code) but I'm not sure.  Have other seen this on our Jenkins and
solved it?

Scott

[1] https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/8.0/40/console

_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build