weiqingy commented on PR #895: URL: https://github.com/apache/flink-agents/pull/895#issuecomment-4938878056
Note on this PR's own CI, to avoid a misread: the two red legs (`it-java [flink-1.20]` and `it-java [java-21] [flink-2.0]`) are the `llama-server` segfault flake this PR targets — `llama-server process has terminated: signal: segmentation fault (core dumped)`. This change only adds a workflow file and touches no test or build path, so it cannot itself cause a test failure. This PR cannot demonstrate the fix on its own CI: a `workflow_run` companion runs only from the copy of the file on the default branch, so it is not active for this PR's run. Once merged it activates for every subsequent "Flink Agents CI" run, including pull-request runs — a failed integration-test leg is re-run on a fresh runner and its check flips to green, while a genuine failure that reproduces on every fresh runner stays red. That is the intended signal: a flaky failure auto-heals, a real one persists. I validated the mechanism end-to-end on a fork (companion on the fork's default branch): a failed integration-test-named job was re-run on a fresh runner and the run flipped green, a non-matching job was left untouched, and the `run_attempt` cap stopped the retry chain. This mirrors the existing `pr_labeler` / `issue_labeler` companions, which likewise run from the default branch via `workflow_run`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
