Skip to content

[FLAKE] should surface components in its status #2628

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

Closed
perdasilva opened this issue Feb 15, 2022 · 2 comments
Closed

[FLAKE] should surface components in its status #2628

perdasilva opened this issue Feb 15, 2022 · 2 comments
Labels
kind/flake Categorizes issue or PR as related to a flaky test.

Comments

@perdasilva
Copy link
Collaborator

perdasilva commented Feb 15, 2022

Description

Operator API 
  should surface components in its status
  /home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/operator_test.go:73

[BeforeEach] Operator API
  /home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/operator_test.go:41
[It] should surface components in its status
  /home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/operator_test.go:73
STEP: eventually having a status that contains its component label selector
STEP: eventually listing a single component reference
STEP: eventually listing multiple component references


• Failure [90.305 seconds]
Operator API
/home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/operator_test.go:31
  should surface components in its status [It]
  /home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/operator_test.go:73

  Unexpected error:
      <context.deadlineExceededError>: {}
      context deadline exceeded
  occurred

  /home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/util.go:892

  Full Stack Trace
  github.com/operator-framework/operator-lifecycle-manager/test/e2e.awaitPredicates({0x32ad530, 0xc001b372c0}, {0x[328](https://github.com/operator-framework/operator-lifecycle-manager/runs/5201544420?check_suite_focus=true#step:4:328)e798, 0xc001d28b80}, {0xc000e2cc78, 0x1, 0x328cee8})
  	/home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/util.go:892 +0x213
  github.com/operator-framework/operator-lifecycle-manager/test/e2e.componentRefEventuallyExists({0x328e798, 0xc001d28b80}, 0x1, 0xc001aca850)
  	/home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/operator_test.go:408 +0xfc
  github.com/operator-framework/operator-lifecycle-manager/test/e2e.glob..func19.2()
  	/home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/operator_test.go:181 +0xe93
  github.com/operator-framework/operator-lifecycle-manager/test/e2e.TestEndToEnd(0xf908f9)
  	/home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/e2e_test.go:59 +0x268
  testing.tRunner(0xc000aa24e0, 0x3005598)
  	/opt/hostedtoolcache/go/1.17.6/x64/src/testing/testing.go:1259 +0x102
  created by testing.(*T).Run
  	/opt/hostedtoolcache/go/1.17.6/x64/src/testing/testing.go:1306 +0x35a
@perdasilva perdasilva added the kind/flake Categorizes issue or PR as related to a flaky test. label Feb 15, 2022
@perdasilva perdasilva changed the title [Flake] should surface components in its status [FLAKE] should surface components in its status Feb 16, 2022
@akihikokuroda
Copy link
Member

duplicate with #2581

@perdasilva
Copy link
Collaborator Author

Closing as it's duplicate of #2581

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test.
Projects
None yet
Development

No branches or pull requests

2 participants