idaholab / moose

Multiphysics Object Oriented Simulation Environment
https://www.mooseframework.org
GNU Lesser General Public License v2.1
1.79k stars 1.05k forks source link

Reduce time for tests that commonly timeout #25712

Open loganharbour opened 1 year ago

loganharbour commented 1 year ago

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.

loganharbour commented 1 year ago

@GiudGiud I know you might have had an issue for the format output but I can't seem to find it

GiudGiud commented 1 year ago

Daniel has this one https://github.com/idaholab/moose/issues/25597

dschwen commented 1 year ago

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)?

loganharbour commented 1 year ago

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

GiudGiud commented 1 year ago

Saw this one just now [300.0s] TIMEOUT misc/check_error.missing_function_file_test FAILED (TIMEOUT) [FINISHED]

https://civet.inl.gov/job/1817302/

loganharbour commented 1 year ago

Saw this one just now [300.0s] TIMEOUT misc/check_error.missing_function_file_test FAILED (TIMEOUT) [FINISHED]

https://civet.inl.gov/job/1817302/

I think this is a docker issue

lindsayad commented 1 year ago

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