-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Let tests fail gracefully if no devices are found [14.0.x] #44042
Let tests fail gracefully if no devices are found [14.0.x] #44042
Conversation
type bugfix |
backport #44036 |
please test |
cms-bot internal usage |
If more than one device is available, run the tests on all available devices.
If more than one device is available, run the tests on all available devices. Replace elements_with_stide with uniform_elements.
If more than one device is available, run the tests on all available devices. Replace elements_with_stide with uniform_elements.
If more than one device is available, run the tests on all available devices. Replace elements_with_stide with uniform_elements.
63af9c9
to
2d3d571
Compare
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b3eb64/37614/summary.html Comparison SummarySummary:
|
+1 |
+heterogeneous |
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @antoniovilela, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Let alpaka-based tests that require a device fail gracefully if there are no available devices on the given platform, instead of crashing or succeeding silently.
If more than one device is available, run the tests on each device.
PR validation:
Unit tests pass.
If there are no devices, the tests pass with an informational message instead of failing with a segmentation violation.
Backport status:
Backport of #44036, to make sure test failures do not go undetected in the production branch.