-
Notifications
You must be signed in to change notification settings - Fork 111
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
Tests fail due to global instances destroyed #611
Comments
calgray
changed the title
Test execution fails due to global instances destroyed
Tests fail due to global instances destroyed
Jan 9, 2024
#572 resolved the issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In some situations it's important that tests can be executed while other static objects are not yet destroyed such as when using NVCC-compiled cuda kernels. Running tests after main finishes causes problems.
Expected Behavior
Updating from 1.1.8 to 2.0.1 should keep cuda tests passing or provide a way to execute tests from main().
Actual Behavior
Using an empty main executes cuda tests after the cuda context has ended. Alternatively, executing the runner from main does not read command line arguments.
Steps to Reproduce the Problem
or
boost::ut::cfg<boost::ut::override>.run();
from main and the test passes, but arguments such--help
do nothing.Specifications
The text was updated successfully, but these errors were encountered: