Tests: improve CUDA support detection #985
Merged
+26
−14
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.
Most of the tests require CUDA capabilities; only some of them were previously marked as such and skipped when no CUDA was available, the rest of them were left to fail.
This PR adds a pytest hook that turns the Torch
Torch not compiled with CUDA enabled
assertion error intopytest.skip
, and a Pytest fixture that a test can use to assert that CUDA support is available too.On a machine where
make cpuonly
passes (namely in alinux/amd64
Docker box), running tests onmain
(53f8af8) results inWith this PR, the result is a more sensible
(though whether
test_nvidia_transform
should (partially) succeed on a machine with no CUDA is anybody's guess).Related to discussion in #984.