cosa CI fails intermittently in checkout scm step
#3372
Assignees
Labels
jira
for syncing to jira
Comments
|
It seems like restarting Jenkins helps this. I wouldn't be surprised if it came back though. |
jlebon
added a commit
to jlebon/fedora-coreos-pipeline
that referenced
this issue
Feb 27, 2023
By default, the jnlp container has a memory request of 256Mi and no memory limit. In 9eed927 ("manifests/jenkins: set resource limits and requests for jnlp container"), we added an explicit memory limit so that we don't inherit the default 10G memory limit from the limitrange in the RHCOS OpenShift project. We set it to 256Mi since that's what the default memory *request* was, but it's too little as a hard limit. Bump it to 512Mi. And also bump the request since in this project we try to have requests match what the pod actually needs. Fixes coreos/coreos-assembler#3372.
jlebon
added a commit
to jlebon/fedora-coreos-pipeline
that referenced
this issue
Feb 27, 2023
By default, the jnlp container has a memory request of 256Mi and no memory limit. In 9eed927 ("manifests/jenkins: set resource limits and requests for jnlp container"), we added an explicit memory limit so that we don't inherit the default 10G memory limit from the limitrange in the RHCOS OpenShift project. We set it to 256Mi since that's what the default memory *request* was, but it's too little as a hard limit. Bump it to 512Mi. And also bump the request since in this project we try to have requests match what the pod actually needs. Fixes coreos/coreos-assembler#3372.
jlebon
added a commit
to jlebon/fedora-coreos-pipeline
that referenced
this issue
Feb 27, 2023
By default, the jnlp container has a memory request of 256Mi and no memory limit. In 9eed927 ("manifests/jenkins: set resource limits and requests for jnlp container"), we added an explicit memory limit so that we don't inherit the default 10G memory limit from the limitrange in the RHCOS OpenShift project. We set it to 256Mi since that's what the default memory *request* was, but it's too little as a hard limit. Bump it to 512Mi. And also bump the request since in this project we try to have requests match what the pod actually needs. While we're here, add a comment about why we set these values. Fixes coreos/coreos-assembler#3372.
jlebon
added a commit
to jlebon/fedora-coreos-pipeline
that referenced
this issue
Feb 27, 2023
By default, the jnlp container has a memory request of 256Mi and no memory limit. In 9eed927 ("manifests/jenkins: set resource limits and requests for jnlp container"), we added an explicit memory limit so that we don't inherit the default 10G memory limit from the limitrange in the RHCOS OpenShift project. We set it to 256Mi since that's what the default memory *request* was, but it's too little as a hard limit. Most of the time, the jnlp unexplicably dies, but at least once, I saw it fail with: ``` java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached ``` Bump it to 512Mi. And also bump the request since in this project we try to have requests match what the pod actually needs. While we're here, add a comment about why we set these values. Fixes coreos/coreos-assembler#3372.
jlebon
added a commit
to coreos/fedora-coreos-pipeline
that referenced
this issue
Feb 27, 2023
By default, the jnlp container has a memory request of 256Mi and no memory limit. In 9eed927 ("manifests/jenkins: set resource limits and requests for jnlp container"), we added an explicit memory limit so that we don't inherit the default 10G memory limit from the limitrange in the RHCOS OpenShift project. We set it to 256Mi since that's what the default memory *request* was, but it's too little as a hard limit. Most of the time, the jnlp unexplicably dies, but at least once, I saw it fail with: ``` java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached ``` Bump it to 512Mi. And also bump the request since in this project we try to have requests match what the pod actually needs. While we're here, add a comment about why we set these values. Fixes coreos/coreos-assembler#3372.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've seen this some recently where the
checkout scmstep fails:This happened in PR-3371#1 and also consistently 3 or 4 times in #3366 (though those CI runs have been garbage collected at this point).
The text was updated successfully, but these errors were encountered: