Skip to content

Add per-component build_timeout for system test Docker builds#848

Open
PranjalManhgaye wants to merge 3 commits into
precice:developfrom
PranjalManhgaye:feature/840-build-timeout
Open

Add per-component build_timeout for system test Docker builds#848
PranjalManhgaye wants to merge 3 commits into
precice:developfrom
PranjalManhgaye:feature/840-build-timeout

Conversation

@PranjalManhgaye

Copy link
Copy Markdown
Collaborator

Summary

  • add optional build_timeout to components in components.yaml (build step only)
  • resolve per-test build timeout as the maximum across distinct participants
  • set dumux-adapter : build_timeout: 1800 for long Dumux Docker builds
  • Document separate build vs run/compare timeouts in readme
    fixes Timeout for building system tests containers #840

Fixes precice#840. Components can set build_timeout in components.yaml; each test
uses the max across its participants. DuMuX builds get 1800s by default.

@MakisH MakisH left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for implementing! Here are some comments before testing on GHA.

Comment thread changelog-entries/848.md Outdated
Comment thread tools/tests/metadata_parser/metdata.py Outdated
Comment thread tools/tests/systemtests/Systemtest.py
Comment thread tools/tests/components.yaml Outdated
Comment thread tools/tests/README.md Outdated
Comment thread tools/tests/README.md Outdated
Use past-tense changelog, int | None typing, 600s build timeouts for
DuMuX and SU2, 300s default run/compare timeout, and clarify max
build timeout behavior in docs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Timeout for building system tests containers

2 participants