You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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: