-
Notifications
You must be signed in to change notification settings - Fork 830
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
Skip all known flaky tests #6634
Conversation
3afd4b2
to
3c5e97f
Compare
3c5e97f
to
ac9dbca
Compare
TEST_TIMEOUT ?= 25m | ||
# 30 minutes is the upper bound defined for all tests, the longer running ones at the time of writing are XDC tests. The | ||
# 30 minute timeout is also defined in run-tests.yml | ||
TEST_TIMEOUT ?= 30m |
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.
We actually wanted to leave this timeout lower than the timeout defined in run-tests.yml
If the GHA times out while the tests are still running it will not produce any output logs and we have no way of telling which tests are taking longer than expected.
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.
Gave some grace time in #6648
Follow up to temporalio#6634, the following tests are still flaky: ``` TestTaskWriterShutdown TestVersioningFunctionalSuite/TestDispatchRetry TestUpdateWorkflowSdkSuite/TestUpdateWorkflow_TimeoutWorkflowAfterUpdateAccepted ``` Also increased XDC timeout to 40 minutes since those tests occasionally time out.
Follow up to temporalio#6634, the following tests are still flaky: ``` TestTaskWriterShutdown TestVersioningFunctionalSuite/TestDispatchRetry TestUpdateWorkflowSdkSuite/TestUpdateWorkflow_TimeoutWorkflowAfterUpdateAccepted ``` Also increased XDC timeout to 40 minutes since those tests occasionally time out.
What changed?
Skipped all known flaky tests.
Also increased
TEST_TIMEOUT
in theMakefile
to30m
to allow XDC tests to span the entire allowed time specified inrun-tests.yml
.Why?
Make CI stable again. We'll need to triage reenabling and fixing these tests over time.
How did you test it?
How did you test it?!