Open loganharbour opened 1 year ago
@GiudGiud I know you might have had an issue for the format output but I can't seem to find it
Daniel has this one https://github.com/idaholab/moose/issues/25597
By "removing timing" do you mean shaving off runtime by shortening / simplifying the test, or by not timing it (i.e. increasing the timeout to infinity)?
By "removing timing" do you mean shaving off runtime by shortening / simplifying the test, or by not timing it (i.e. increasing the timeout to infinity)?
This one: shaving off runtime by shortening / simplifying the test
Saw this one just now [300.0s] TIMEOUT misc/check_error.missing_function_file_test FAILED (TIMEOUT) [FINISHED]
Saw this one just now [300.0s] TIMEOUT misc/check_error.missing_function_file_test FAILED (TIMEOUT) [FINISHED]
I think this is a docker issue
I just added a bunch of modules tests which all timed out in a debug run on https://civet.inl.gov/job/1825600/. @grmnptr quite a few are the new segregated tests
Reason
This is a standing issue to keep track of tests that commonly timeout on civet. The timing for these tests should be decreased where possible.
Framework
Modules
Design
Reduce the timing of the associated tests in a way that does not remove the behavior that was being tested.
Impact
No negative impact if the proper capability is still being tested. Will hopefully lead to less manual intervention in testing.