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
Currently the deterministic tests are run for the legacy CUDA code. Necessarily they will always fail due to the different numerics. i.e. We rely on the statistical integration tests for correctness and to detect meaningful change.
It would be helpful to (1) have the deterministic tests always work ("ctest -L deterministic") and (2) catch changes on Volta, which I think is a safe reference for now. Do we add reference data or disable the numerical checks for now?
The text was updated successfully, but these errors were encountered:
I'm going to work with separated deterministic test for CUDA code as @jtkrogel mentioned. As a first step, I'll disable the deterministic test for CUDA with the current reference now as @ye-luo comment in order to avoid confusion.
Currently the deterministic tests are run for the legacy CUDA code. Necessarily they will always fail due to the different numerics. i.e. We rely on the statistical integration tests for correctness and to detect meaningful change.
It would be helpful to (1) have the deterministic tests always work ("ctest -L deterministic") and (2) catch changes on Volta, which I think is a safe reference for now. Do we add reference data or disable the numerical checks for now?
The text was updated successfully, but these errors were encountered: