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

[Scott Marlow <smarlow@xxxxxxxxxx>]

I ran the same job [2] again and it didn't fail this time.  Note that
the [2] job is started by [3].  I did see the same failure yesterday
as well.

Scott

[2] https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/8.0/41/console
[3] https://ci.eclipse.org/jakartaee-tck/job/eftl-jakartaeetck-certification/

On Thu, Jan 16, 2020 at 10:14 PM 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