[ci] skip Dask tests on GPU builds #5741
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jmoralez
approved these changes
Feb 25, 2023
|
thanks for the quick review @jmoralez ! |
|
This pull request has been automatically locked since there has not been any recent activity since it was closed. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Reverts the changes from #5292.
Since I merged that PR, the
test_dask.pytests have been VERY flaky on GPU builds. My unscientific estimate is that 60% of commits since then have had at least one Azure DevOps GPU job fail.This PR proposes skipping those tests again, to reduce the required manual effort of re-running jobs and to improve the contribution experience for outside contributors.
I'm using #5713 to test fixes, but for now I think we should just skip these flaky tests again 😞