weiqingy commented on PR #892: URL: https://github.com/apache/flink-agents/pull/892#issuecomment-4955164840
Rebased onto current `main` and squashed out the empty re-trigger commits, so this is now a single commit against a base that includes #896. One correction to the CI triage above: the `it-python` py4j failure was described there as an environmental / base failure. It was not — it was an in-repo test bug (the MCP e2e test forking the PyFlink process and corrupting the Py4J gateway), now fixed by #896. It remains true that it was never caused by this PR. Details on #893. That leg should therefore be clean on this run. The `llama-server` segfault is unaffected by #896 and can still redden a leg at random; that one is tracked in #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]
