We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug The bug will cause test failing so we have to disable the assertion for now.
Edited on Apr 6, 2021 -- it's now also failing for Cassandra sometimes.
To Reproduce Is the issue reproducible?
Steps to reproduce the behavior: A clear and concise description of the reproduce steps. Remove the three lines under the TODO
Expected behavior A clear and concise description of what you expected to happen. Fix the test and letting test pass with the assertion.
Screenshots N/A
Additional context #3532
The text was updated successfully, but these errors were encountered:
https://buildkite.com/uberopensource/cadence-server/builds/10120#2be36cee-631a-4254-856c-d37b3e105ded
--- FAIL: TestIntegrationSuite/TestCronWorkflow (8.51s) -- | integrationTest.go:1251: | Error Trace: integrationTest.go:1251 | Error: Not equal: | expected: 0 | actual : 2 | Test: TestIntegrationSuite/TestCronWorkflow | Messages: Still Flaky?: backoffSeconds: 2 ((1617766143031000000-1617766140927000000) - (1617766141031000000-1617766141030000000)), targetBackoffSeconds: 3
Sorry, something went wrong.
No branches or pull requests
Describe the bug
The bug will cause test failing so we have to disable the assertion for now.
Edited on Apr 6, 2021 -- it's now also failing for Cassandra sometimes.
To Reproduce
Is the issue reproducible?
Steps to reproduce the behavior:
A clear and concise description of the reproduce steps.
Remove the three lines under the TODO
Expected behavior
A clear and concise description of what you expected to happen.
Fix the test and letting test pass with the assertion.
Screenshots
N/A
Additional context
#3532
The text was updated successfully, but these errors were encountered: