Increase pytest execution timeout for Dask test backfill integration #26967
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Seems like #26831 a bit broke main tests for Dask Executor.
Testing API Always CLI Core Integration Other Providers WWW. Test Core executed with this setup:
I’m not sure but seems like test cases within
unittests.TestCaseignore pytest timeouts.I just grab randomly couple of previous success run before change base class for tests cases and time to time it ran more than 60s without interruption.
BTW, seems like it is second slowest test in Test Core after after
TestStringifiedDAGs::test_serialization