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
Fix flaky test #1201
Fix flaky test #1201
Conversation
test/integration_test.go
Outdated
var val interface{} | ||
return wfRun.Get(ctx, &val) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
var val interface{} | |
return wfRun.Get(ctx, &val) | |
return wfRun.Get(ctx, nil) |
test/integration_test.go
Outdated
resp, err := ts.libClient.DescribeWorkflowExecution(context.Background(), childWorkflowID, "") | ||
ts.NoError(err) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably not necessary any more? I don't think GetWorkflow needs a runid anyway...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, makes sense that this'd be racy since child-wf-close isn't transactional.
I'd do some small cleanups, but they're pretty foolproof, so 👍-ing now.
What changed?
Fixing flaky integration test since master build was failing. Test was flaky because it was testing that child workflow gets terminated when parent workflow finishes. The test was running into race condition.
Why?
How did you test it?
pipeline run.
Potential risks