Skip to content

Integration tests may be flaky #2789

Closed
Closed

Description

@cjihrig

#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

Current main commit: d62a39e228710cb8a824e47a833bdb5c547a48f9
Actions link: https://github.com/kubernetes-client/javascript/actions/runs/22745752711/job/65969071425

Activity

  1. mstruebing commented on Mar 6, 2026

    @mstruebing
    Member

    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.

  2. cjihrig commented on Mar 6, 2026

    @cjihrig
    ContributorAuthor

    @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.

  3. brendandburns commented on Mar 16, 2026

    @brendandburns
    Contributor

    @cjihrig I would close it for now, if it becomes a major problem we can address it.

  4. cjihrig commented on Mar 16, 2026

    @cjihrig
    ContributorAuthor

    Ack

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions