While #735 added a timeout for the solver execution in the system tests, the building step is still covered by the global timeout, and the relation between the two is a bit tangled.
Since some components take longer to build, we would need a timeout for building. Since different components take different time to build, having the timeout at the component level would make sense.
This would currently help at least the DuMux adapter (see #822) and solids4foam (see #838), and would let us make the global timeout shorter, which would be very helpful for debugging.
For example:
dumux-adapter:
repository: https://github.com/precice/dumux-adapter
template: component-templates/dumux-adapter.yaml
+ build_timeout: 600
build_arguments:
PLATFORM:
description: Dockerfile platform used
default: "ubuntu_2404"
PRECICE_REF:
...
While #735 added a timeout for the solver execution in the system tests, the building step is still covered by the global timeout, and the relation between the two is a bit tangled.
Since some components take longer to build, we would need a timeout for building. Since different components take different time to build, having the timeout at the component level would make sense.
This would currently help at least the DuMux adapter (see #822) and solids4foam (see #838), and would let us make the global timeout shorter, which would be very helpful for debugging.
For example:
dumux-adapter: repository: https://github.com/precice/dumux-adapter template: component-templates/dumux-adapter.yaml + build_timeout: 600 build_arguments: PLATFORM: description: Dockerfile platform used default: "ubuntu_2404" PRECICE_REF: ...