A few days ago, I saw more Eclipse CI Jenkins failures due to:
"hudson.plugins.git.GitException: Command "git checkout -f 5b126670c92e6ab800d35100ad1dfa2a4488daa7" returned status code 137"
I noticed that we have defined -Xmx2048 for the Jenkins (Platform TCK) JNLP process but are using whatever the container memory size is, which could be less than 2gb (default is 512mb I think), which could lead to trashing.
If we still have the git OOM problem, next step might be to enable statistics, that might clue us in as to how the TCK build/run jobs are running.
Scott
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
_______________________________________________
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