weiqingy commented on PR #891: URL: https://github.com/apache/flink-agents/pull/891#issuecomment-4937080263
The 2 failing checks are unrelated to this change — the Ollama install step this PR touches actually **succeeds** in both failing jobs (`>>> Downloading ollama-linux-amd64.tar.zst` → `>>> Install complete`), so the retry/propagation fix is working; the failures are downstream of a healthy install. - **it-python [python-3.12] [flink-2.1]**: the local `llama-server` crashes mid-run (`ollama._types.ResponseError: llama-server process has terminated: signal: segmentation fault (core dumped)`). This is the model-server crash, not the installer — intermittent on `main` too (passes ~5/6 runs). [Log](https://github.com/apache/flink-agents/actions/runs/29102229967/job/86393743225). - **it-python [python-3.11] [flink-1.20]**: a py4j/Flink-1.20 classpath failure (`org does not exist in the JVM`, `KeyError: 'p'`), not Ollama-related. The same job fails identically on current `main` ([main run](https://github.com/apache/flink-agents/actions/runs/29080522747/job/86322060047)), so it's pre-existing and flaky. [Log](https://github.com/apache/flink-agents/actions/runs/29102229967/job/86393743236). This PR hardens the install step against transient download 404s; it doesn't address the `llama-server` segfault, which is tracked as the open item on #889. Could you please help re-trigger the two failed jobs? Thanks! -- 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]
