Skip to content

Commit

Permalink
Use a trick to just run GPU tests with buildkite
Browse files Browse the repository at this point in the history
  • Loading branch information
amontoison committed Nov 17, 2023
1 parent 561c70c commit 7a7eb4d
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion test/gpu/gpu.jl
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ function test_ic0(FC, V, M)
x_gpu, stats = cg(A_gpu, b_gpu, M=P, ldiv=true)
r_gpu = b_gpu - A_gpu * x_gpu
@test stats.niter 5
if (FC <: ComplexF64) && (isa(A_gpu, ROCSparseMatrixCSR))
if (FC <: ComplexF64) && typeof(V).name.name == :ROCArray
@test_broken norm(r_gpu) 1e-6
else
@test norm(r_gpu) 1e-8
Expand Down

2 comments on commit 7a7eb4d

@amontoison
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/95522

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.0 -m "<description of version>" 7a7eb4d680fddc534c943f10c2a7b3333975752b
git push origin v0.1.0

Please sign in to comment.