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

Is TestWorkflowLevelSemaphore flakey? #3748

Closed
alexec opened this issue Aug 12, 2020 · 2 comments · Fixed by #3749
Closed

Is TestWorkflowLevelSemaphore flakey? #3748

alexec opened this issue Aug 12, 2020 · 2 comments · Fixed by #3749
Assignees
Labels

Comments

@alexec
Copy link
Contributor

alexec commented Aug 12, 2020

Summary

Is this flakey? Seems to randomly fail.

Diagnostics

    --- FAIL: TestCLISuite/TestWorkflowLevelSemaphore (0.31s)
        cli_test.go:934: 
            	Error Trace:	cli_test.go:934
            	            				when.go:187
            	            				cli_test.go:933
            	Error:      	"Name:                semaphore-wf-level\nNamespace:           argo\nServiceAccount:      default\nStatus:              Pending\nCreated:             Wed Aug 12 10:58:54 -0700 (now)\n" does not contain "Waiting for"
            	Test:       	TestCLISuite/TestWorkflowLevelSemaphore


Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

@sarabala1979 sarabala1979 self-assigned this Aug 12, 2020
@sarabala1979
Copy link
Member

let me take a look

@alexec
Copy link
Contributor Author

alexec commented Aug 12, 2020

@sarabala1979 I'm doing some refactoring (#3749) that should make e2e tests more robust - can I steal this issue from you please?

@alexec alexec linked a pull request Aug 13, 2020 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants