weiqingy commented on PR #895:
URL: https://github.com/apache/flink-agents/pull/895#issuecomment-4955190493

   Rebased onto current `main` (which now includes #896) and updated the 
description.
   
   The scope of this PR has narrowed. It previously covered two failure modes; 
the py4j gateway failure turned out to be an in-repo test bug rather than an 
environmental one, and #896 has fixed it. What remains is the Ollama 
`llama-server` segfault alone, which is unaffected by that fix.
   
   The case for the rerun is now easier to state precisely: on the first 
post-#896 `main` run 
([29227640397](https://github.com/apache/flink-agents/actions/runs/29227640397)),
 10 of the 11 integration jobs passed and the single failure was purely the 
segfault — enough on its own to turn the run red. Re-running the workflow 
re-rolls all 11 jobs; this companion re-runs only the one that failed.
   
   The earlier per-job failure-rate figures counted both modes and have been 
dropped from the description rather than restated. Whether the residual 
segfault fires often enough to justify automating the rerun is worth judging 
from the next few `main` runs, and that is being tracked on #893.
   


-- 
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]

Reply via email to