You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#2788 only bumped the @types/node dependency. The first CI run failed in the integration tests. I re-ran the test and it passed, so the test may be flaky.
Run npm run integration-test
> @kubernetes/client-node@2.0.0 integration-test
> tsx src/test/integration/index.ts
Integration testing
Creating namespace patch-ns-aa1gn
Namespace created with initial label.
Patching namespace patch-ns-aa1gn to replace labels
Namespace patched with new label.
Creating pod cp-test-pod-l2564fj
Waiting for pod to be ready...
node:internal/modules/run_main:107
triggerUncaughtException(
^
AssertionError [ERR_ASSERTION]: Pod did not become ready in time
false !== true
at cpFromPod (/home/runner/work/javascript/javascript/src/test/integration/cpFromPod.ts:47:12)
at async <anonymous> (/home/runner/work/javascript/javascript/src/test/integration/index.ts:8:1) {
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: false,
expected: true,
operator: 'strictEqual',
diff: 'simple'
}
Node.js v24.14.0
We are waiting for 30 seconds, that should be enough usually for this type of action and this small of a container (busybox).
I would most likely suspect a very slow network connection or the registry not being available for whatever reason.
The other thing could be that the runner was under very high load if they are shared in some kind.
Activity
mstruebing commentedon Mar 6, 2026
We are waiting for 30 seconds, that should be enough usually for this type of action and this small of a container (busybox).
I would most likely suspect a very slow network connection or the registry not being available for whatever reason.
The other thing could be that the runner was under very high load if they are shared in some kind.
cjihrig commentedon Mar 6, 2026
@mstruebing do you think we should increase the timeout or just close this issue? I'm fine either way, I just wanted to raise what I saw.
brendandburns commentedon Mar 16, 2026
@cjihrig I would close it for now, if it becomes a major problem we can address it.
cjihrig commentedon Mar 16, 2026
Ack