-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[CI] Refactor of tvm.testing.requires_* annotations #11313
Conversation
@mehrdadh I expect this to conflict with these changes in PR#11294. Between the two, your PR takes priority, as it is solving an immediate issue. If all goes well, I don't expect the conflict to be difficult to resolve, as the corresponding change after this refactor would be to replace |
Previously, the same message was given regardless of why a test couldn't be run. This has been split up into separate checks for TVM cmake options in `config.cmake`, enabled targets in `TVM_TEST_TARGETS` environment variable, and checks for available hardware.
4a5087f
to
7bd8211
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These were enabled in apache#11294, then erroneously disabled in apache#11313. This applies the same fix as in apache#11294, checking the `ANDROID_SERIAL_NUMBER` to determine if Hexagon tests can execute at runtime, but using the refactored `pytest.skipif` messages introduced in apache#11313.
These were enabled in apache#11294, then erroneously disabled in apache#11313. This applies the same fix as in apache#11294, checking the `ANDROID_SERIAL_NUMBER` to determine if Hexagon tests can execute at runtime, but using the refactored `pytest.skipif` messages introduced in apache#11313.
* [Hexagon][CI] Re-enable Hexagon tests in CI These were enabled in #11294, then erroneously disabled in #11313. This applies the same fix as in #11294, checking the `ANDROID_SERIAL_NUMBER` to determine if Hexagon tests can execute at runtime, but using the refactored `pytest.skipif` messages introduced in #11313. * Fixed circular dependency, but feels somewhat ugly
* [Hexagon][CI] Re-enable Hexagon tests in CI These were enabled in apache#11294, then erroneously disabled in apache#11313. This applies the same fix as in apache#11294, checking the `ANDROID_SERIAL_NUMBER` to determine if Hexagon tests can execute at runtime, but using the refactored `pytest.skipif` messages introduced in apache#11313. * Fixed circular dependency, but feels somewhat ugly
This PR has two main goals.
config.cmake
, disabled inTVM_TEST_TARGETS
, or no device available).@tvm.testing.requires_*
decorators maintain the same semantics, skipping a test unless both compile-time and run-time support are present. This adds an optional argument to indicate that the test does not require a physical device (e.g. to require cuda library support without requiring a cuda-capable GPU:@requires_cuda(support_required="compile-only")
cc @Mousius @areusch @driazati