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
The batched_dla unit test runtime is consistently near or hitting timeout of 1500 seconds in Cuda and Hip nightly builds. This will need to be reduced before the 4.0 release to reliably pass CI with the Trilinos snapshot.
A couple options to reduce time include splitting the tests in the cpp file into separate cpp files and/or reducing problem sizes if feasible. Other thoughts?
This is also occurring with Trilinos e.g. trilinos/Trilinos#11235 , though for those builds with 3.7.00 I hope the issue can be mitigated with the RUN_SERIAL option (assuming tests are run with parallelism)
The
batched_dla
unit test runtime is consistently near or hitting timeout of 1500 seconds in Cuda and Hip nightly builds. This will need to be reduced before the 4.0 release to reliably pass CI with the Trilinos snapshot.A couple options to reduce time include splitting the tests in the cpp file into separate cpp files and/or reducing problem sizes if feasible. Other thoughts?
This is also occurring with Trilinos e.g. trilinos/Trilinos#11235 , though for those builds with 3.7.00 I hope the issue can be mitigated with the
RUN_SERIAL
option (assuming tests are run with parallelism)Reproducer (Weaver rhel8 queue, Cuda build):
The text was updated successfully, but these errors were encountered: