[ci] Time out integration test when the host PC is unresponsive - #1081
Open
JSUYA wants to merge 1 commit into
Open
[ci] Time out integration test when the host PC is unresponsive#1081JSUYA wants to merge 1 commit into
JSUYA wants to merge 1 commit into
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2c2700cd01
ℹ️ 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".
JSUYA
force-pushed
the
ci-integration-test-timeout
branch
from
August 11, 2026 05:22
2c2700c to
aeccd15
Compare
If the host PC running the self-hosted runner is offline or has an unstable network, the integration test run can stay queued until GitHub's 24-hour limit (e.g. ~15 hours in https://github.com/flutter-tizen/plugins/actions/runs/31377384649/attempts/1 where the job never left the queued state). - Add a watchdog job on a GitHub-hosted runner that fails the run if integration_test is stuck in the queue for 15 minutes while the runner is idle (i.e. offline rather than busy with another run). timeout-minutes cannot cover this case because it only counts after a job starts. Cancelling the run is attempted best-effort only, since fork PRs get a read-only GITHUB_TOKEN. Being a job in the same workflow, the watchdog is re-run together with integration_test. - Add timeout-minutes: 60 to the integration_test job as a backstop for jobs that hang after starting.
JSUYA
force-pushed
the
ci-integration-test-timeout
branch
from
August 12, 2026 11:36
aeccd15 to
3a071cd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If the host PC running the self-hosted runner is offline or has an unstable network, the integration test run can stay queued until GitHub's 24-hour limit.
Add a watchdog job on a GitHub-hosted runner that fails the run if integration_test is stuck in the queue for 15 minutes while the runner is idle (i.e. offline rather than busy with another run). timeout-minutes cannot cover this case because it only counts after a job starts. Cancelling the run is attempted best-effort only, since fork PRs get a read-only GITHUB_TOKEN. Being a job in the same workflow, the watchdog is re-run together with integration_test.
Add timeout-minutes: 60 to the integration_test job as a backstop for jobs that hang after starting.