-
Notifications
You must be signed in to change notification settings - Fork 94
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
[RELEASE] dask-cuda v0.14 #298
Merged
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
[gpuCI] Auto-merge branch-0.13 to branch-0.14 [skip ci]
[gpuCI] Auto-merge branch-0.13 to branch-0.14 [skip ci]
[gpuCI] Auto-merge branch-0.13 to branch-0.14 [skip ci]
[REVIEW] Publish branch 0.14 to conda
[gpuCI] Auto-merge branch-0.13 to branch-0.14 [skip ci]
[gpuCI] Auto-merge branch-0.13 to branch-0.14 [skip ci]
Fix behavior for `memory_limit=0`
The default behavior of `serialize` (and thus `serialize_bytes`) is to capture any serialization errors as messages. The result is the error gets raises on deserialization. However for spilling, this means that we fail to spill and raise that error only after trying to restore that data. Instead go ahead and raise the error when trying to spill to avoid thinking content has spilled successfully (when that is not the case) and thus losing it.
Raise serialization errors when spilling
Fix dask-cuda-worker memory_limit
Add NVTX annotations for spilling
[REVIEW] Skip existing on conda uploads [skip-ci]
Multi-node benchmarks
Add docs for UCX
Add `--runs` argument to CuPy benchmark
[DOC] Fixing LocalCUDACluster example. Adding README link to docs
Codecov Report
|
Add `nfinal` argument to shuffle_group, required in Dask >= 2.17
rerun tests |
2 similar comments
rerun tests |
rerun tests |
Update changelog for 0.14 [skip ci]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
❄️ Code freeze for
branch-0.14
and v0.14 releaseWhat does this mean?
Only critical/hotfix level issues should be merged into
branch-0.14
until release (merging of this PR).What is the purpose of this PR?
branch-0.14
intomaster
for the release