Adding back gitlab timeout because some jobs are hanging on the get_source step - #7423
Conversation
|
|
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2e7f9c4f95
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| {% endfor %} | ||
| {% for variant, scenario, build_required in scenario_pairs %} | ||
| system_tests_run_{{library}}_{{scenario}}_{{variant}}: | ||
| timeout: 15 minutes |
There was a problem hiding this comment.
Apply the hang timeout to every generated job
When get_sources hangs on a setup, build, or parametric job, this timeout has no effect because it is emitted only for jobs in scenario_pairs. The generated setup, system_tests_build_*, and system_tests_run_*_PARAMETRIC_* jobs all extend the same .system_tests_base, which does not define a timeout, so those jobs can still remain stuck until the broader project timeout. Apply the timeout at the shared/default level, or add it to every generated job category that can encounter the hanging runner phase.
Useful? React with 👍 / 👎.
Motivation
Changes
Workflow
🚀 Once your PR is reviewed and the CI green, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist
tests/ormanifests/is modified ? I have the approval from R&P teambuild-XXX-imagelabel is present