Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Flaky Test] Registry Cache Extension Tests [It] should create Shoot with registry-cache extension enabled with caches for Shoot system components, delete Shoot #290

Open
3 tasks
ialidzhikov opened this issue Nov 15, 2024 · 0 comments · May be fixed by #303
Assignees
Labels
area/testing Testing related kind/flake Tracking or fixing a flaky test

Comments

@ialidzhikov
Copy link
Member

ialidzhikov commented Nov 15, 2024

How to categorize this issue?

/area testing
/kind flake

Which test(s)/suite(s) are flaking:

  [FAIL] Registry Cache Extension Tests [It] should create Shoot with registry-cache extension enabled with caches for Shoot system components, delete Shoot [cache]
  /home/prow/go/src/github.com/gardener/gardener-extension-registry-cache/test/e2e/cache/create_enabled_delete_shoot_system_components.go:40

CI link:

Reason for failure:

  [FAILED] Expected success, but got an error:
      <*retry.Error | 0xc0004b20c0>: 
      retry failed with context deadline exceeded, last error: shoot "e2e-cache-ssc" was not successfully reconciled
      {
          ctxError: <context.deadlineExceededError>{},
          err: <*errors.errorString | 0xc00055ea70>{
              s: "shoot \"e2e-cache-ssc\" was not successfully reconciled",
          },
      }
  In [It] at: /home/prow/go/src/github.com/gardener/gardener-extension-registry-cache/test/e2e/cache/create_enabled_delete_shoot_system_components.go:40 @ 11/15/24 14:30:55.063

Anything else we need to know:

Task:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing Testing related kind/flake Tracking or fixing a flaky test
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants