gnodet commented on PR #25423:
URL: https://github.com/apache/camel/pull/25423#issuecomment-5237989986

   ## ✅ Local IT results for `422450e1ba15`
   
   No container-upgrade-related regressions detected. Resource constraint 
timeouts noted below are not caused by this version bump.
   
   **Test-infra module**: `camel-test-infra-ollama`
   **Components tested** (representative subset): `camel-langchain4j-chat`, 
`camel-openai`
   
   | Component | Tests | Passed | Failed | Errors | Skipped | Status |
   |-----------|-------|--------|--------|--------|---------|--------|
   | `camel-langchain4j-chat` | 14 | 13 | 0 | 1 | 0 | ⚠️ timeout |
   | `camel-openai` | 18+ | 18+ | 0 | 0 | 0 | ⚠️ fork timeout |
   
   ### Resource constraint notes (not caused by this PR)
   
   **langchain4j-chat:** `testSendMessageWithPrompt` timed out after 184s 
(`dev.langchain4j.exception.TimeoutException: request timed out`). The 
remaining 13 tests all passed. This is an LLM inference timeout under resource 
constraints, not a behavioral change.
   
   **openai:** 186 unit tests passed, 18 ITs passed (MCP tools, embeddings, 
chat completions all green). The failsafe fork timed out during 
`OpenAIMcpParallelToolExecutionIT` after 11 minutes total — the parallel tool 
execution test is resource-intensive when running locally with Ollama. All 
completed ITs passed with 0 failures.
   
   ### Untested components (8 total consumers)
   
   The following were not tested as part of the representative subset: 
`camel-langchain4j-agent`, `camel-langchain4j-tools`, `camel-spring-ai-chat`, 
`camel-spring-ai-embeddings`, `camel-spring-ai-image`, 
`camel-spring-ai-vector-store`
   
   > _Local integration tests run by ForgeBot on behalf of @gnodet_
   > _Tests run without `-Dci.env.name` to include ITs disabled on GitHub 
Actions CI_


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