weiqingy commented on PR #892: URL: https://github.com/apache/flink-agents/pull/892#issuecomment-4937080392
The 2 failing checks are unrelated to this change — this PR only adds `timeout-minutes` to three jobs, so it changes *how fast a hang surfaces*, not whether any test passes. The Ollama install succeeds in both jobs (`>>> Install complete`). - **it-java [java-21] [flink-2.0]**: the local `llama-server` crashes (`io.github.ollama4j.exceptions.OllamaException: llama-server process has terminated` in `YamlLoaderIntegrationTest` / `ChatModelIntegrationTest`). This is the model-server crash — intermittent on `main` too (this job passes 6/6 recent runs). [Log](https://github.com/apache/flink-agents/actions/runs/29102238478/job/86393772044). - **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 failure count is identical to the same job on #891 (which doesn't touch `ci.yml`), and 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/29102238478/job/86393771978). The `llama-server` segfault is exactly the intermittent hang this PR's timeouts are meant to bound (rather than fix) — the root-cause discussion is 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]
