| Re: [ee4j-build] Unexpected Jenkins failure with "git checkout" returning status code 137... |
On Tue, Jan 21, 2020 at 11:38 AM arjan tijms <arjan.tijms@xxxxxxxxx> wrote: > > 1.33 it seems ;) Nice, so we can cross off the durable-task as the possible cause. I'm guessing that it could help to verify that: 1. Our TCK environment is being cleaned up after test step, even in the case of abnormal termination. 2. TCK test steps are configured to have enough resources (e.g. CPU + memory). See [1][2][3]. 3. Check if org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator.websocketConnectionTimeout is configured for our Jenkins. Perhaps increasing the org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator.websocketConnectionTimeout setting to be (reasonably) longer than 10 seconds to see if that avoids the previously mentioned timeout induced failure. Scott [1] https://stackoverflow.com/questions/52442333/configure-kubernetes-cpu-memory-request-and-limit-for-a-jenkins-slaves-created-w [2] https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#meaning-of-cpu [3] https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#meaning-of-memory