Repository navigation
Expect GPUArrays 12.1.1's 2-arg show of GPU arrays in tests and docs - #3405
Merged
Merged
Conversation
GPUArrays 12.1.1 (JuliaGPU/GPUArrays.jl#429) shows GPU arrays as a call to their storage type, e.g. `CuArray([1, 2])`. A `CuSparseVector` now shows as `sparsevec(CuArray(...), CuArray(...), n)`, which evaluates to an equal vector, and the tuple returned by `findmax` in the array usage docs shows its arrays the same way. The test environment requires that release, so the old-dependencies job doesn't pick 12.1.0.
Contributor
CUDA.jl BenchmarksDetails
This comment was automatically generated by workflow using github-action-benchmark. |
This file contains hidden or 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
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.
GPUArrays 12.1.1 (JuliaGPU/GPUArrays.jl#429) shows GPU arrays as a call to their storage type, e.g.
CuArray([1, 2]). This broke theCuSparseVectorshow test and afindmaxdoctest on every CUDA job and the docs build (main included, e.g. #3404). The new output evaluates to an equal array, so this updates the expectations, and requires 12.1.1 in the test environment so the old-dependencies job doesn't resolve 12.1.0.