github-actions[bot] commented on PR #27842: URL: https://github.com/apache/camel/pull/27842#issuecomment-6175947598
<!-- ci-tested-modules --> :test_tube: **CI tested the following changed modules:** - `parent` :white_check_mark: **POM dependency changes: targeted tests included** Changed properties: langchain4j-community-version <details><summary>Modules affected by dependency changes (1)</summary> - `:camel-langchain4j-tokenizer` </details> :repeat: **1 test passed only after a retry on JDK 25** (1 retried attempt) <details><summary>Recovered flaky tests on JDK 25 (1)</summary> | Module | Test | Failed attempts | First failure | | --- | --- | --- | --- | | `dsl/camel-jbang/camel-jbang-plugin-tui` | `AiPanelAcpTest.retryResendsTheLastQuestionToTheAgent` | 1 | expected: <2> but was: <1> | > :information_source: These tests did **not** fail the build. Surefire retried them and they passed. > Retries are enabled project-wide by `surefire.rerunFailingTestsCount` in `parent/pom.xml`. </details> --- <details><summary>:microscope: Scalpel shadow comparison — Scalpel: 9 of 703 tested, 3 compile-only — current: 0 all tested</summary> [Maveniverse Scalpel](https://github.com/maveniverse/scalpel) detected **9 affected modules** (current approach: 0). Changed properties: langchain4j-community-version **Skip-tests mode would test 9 modules** (2 direct + 0 downstream), **skip tests for 3** (generated code, meta-modules) <details><summary>:warning: Modules only in Scalpel (9)</summary> - `camel-jbang-mcp` - `camel-jbang-plugin-mcp` - `camel-jbang-plugin-tui` - `camel-jbang-plugin-validate` - `camel-jpa` - `camel-langchain4j-tokenizer` - `camel-launcher-container` - `camel-yaml-dsl-validator` - `camel-yaml-dsl-validator-maven-plugin` </details> <details><summary>Modules Scalpel would test (9)</summary> - `camel-jbang-mcp` ← depends on affected reactor module org.apache.camel:camel-yaml-dsl-validator - `camel-jbang-plugin-mcp` ← depends on affected reactor module org.apache.camel:camel-jbang-core - `camel-jbang-plugin-tui` ← depends on affected reactor module org.apache.camel:camel-yaml-dsl-validator - `camel-jbang-plugin-validate` ← depends on affected reactor module org.apache.camel:camel-yaml-dsl-validator - `camel-jpa` ← effective property camel.surefire.fork.additional-vmargs - `camel-langchain4j-tokenizer` ← effective dep dev.langchain4j:langchain4j-community-dashscope - `camel-launcher-container` ← depends on affected reactor module org.apache.camel:camel-launcher - `camel-yaml-dsl-validator` ← depends on affected reactor module org.apache.camel:camel-catalog - `camel-yaml-dsl-validator-maven-plugin` ← depends on affected reactor module org.apache.camel:camel-yaml-dsl-validator </details> <details><summary>Modules with tests skipped (3)</summary> - `camel-itest` - `camel-yaml-dsl` - `camel-yaml-dsl-deserializers` </details> > :information_source: Shadow mode — Scalpel observes but does not affect test execution. [Learn more](https://github.com/maveniverse/scalpel) </details> <details><summary>All tested modules (37 modules, 4m 54s total)</summary> **Total reactor time:** 4m 54s | Module | Duration | Status | | --- | --- | --- | | Camel :: JBang :: Plugin :: TUI | 53.9s | SUCCESS | | Camel :: JPA | 42.5s | SUCCESS | | Camel :: JBang :: Plugin :: Validate | 25.6s | SUCCESS | | Camel :: Launcher | 23.8s | SUCCESS | | Camel :: JBang :: MCP | 16.3s | SUCCESS | | Camel :: YAML DSL :: Validator | 14.7s | SUCCESS | | Camel :: Catalog :: Camel Catalog | 13.9s | SUCCESS | | Camel :: YAML DSL | 13.7s | SUCCESS | | Camel :: Component DSL | 12.8s | SUCCESS | | Camel :: Kamelet Main | 10.8s | SUCCESS | | Camel :: Docs | 10.1s | SUCCESS | | Camel :: JBang :: Plugin :: Kubernetes | 8.4s | SUCCESS | | Camel :: AI :: LangChain4j :: Tokenizer | 7.6s | SUCCESS | | Camel :: YAML DSL :: Deserializers | 5.8s | SUCCESS | | Camel :: Catalog :: Camel Report Maven Plugin | 5.0s | SUCCESS | | Camel :: Catalog :: Camel Route Parser | 5.0s | SUCCESS | | Camel :: JBang :: Plugin :: Testing | 4.0s | SUCCESS | | Camel :: All Components Sync point | 3.0s | SUCCESS | | Camel :: YAML DSL :: Validator Maven Plugin | 2.6s | SUCCESS | | Camel :: Catalog :: Maven | 2.2s | SUCCESS | | Camel :: YAML DSL :: Maven Plugins | 1.7s | SUCCESS | | Camel :: Catalog :: Suggest (deprecated) | 1.6s | SUCCESS | | Camel :: JBang :: Plugin :: Edit | 1.0s | SUCCESS | | Camel :: Endpoint DSL :: Support | 0.9s | SUCCESS | | Camel :: Assembly | 0.9s | SUCCESS | | Camel :: Catalog :: Dummy Component | 0.9s | SUCCESS | | Camel :: JBang :: Integration tests | 0.8s | SUCCESS | | Camel :: Parent | 0.8s | SUCCESS | | Camel :: Coverage | 0.8s | SUCCESS | | Camel :: JBang :: Plugin :: Generate | 0.8s | SUCCESS | | Camel :: Catalog :: Console | 0.7s | SUCCESS | | Camel :: JBang :: Main | 0.6s | SUCCESS | | Camel :: JBang :: Plugin :: MCP | 0.4s | SUCCESS | | Camel :: Launcher :: Container | 0.4s | SUCCESS | | Camel :: Endpoint DSL | n/a | | | Camel :: Integration Tests | n/a | | | Camel :: JBang :: Core | n/a | | **Top 20 slowest modules:** - `Camel :: JBang :: Plugin :: TUI` (53.9s) - `Camel :: JPA` (42.5s) - `Camel :: JBang :: Plugin :: Validate` (25.6s) - `Camel :: Launcher` (23.8s) - `Camel :: JBang :: MCP` (16.3s) - `Camel :: YAML DSL :: Validator` (14.7s) - `Camel :: Catalog :: Camel Catalog` (13.9s) - `Camel :: YAML DSL` (13.7s) - `Camel :: Component DSL` (12.8s) - `Camel :: Kamelet Main` (10.8s) - `Camel :: Docs` (10.1s) - `Camel :: JBang :: Plugin :: Kubernetes` (8.4s) - `Camel :: AI :: LangChain4j :: Tokenizer` (7.6s) - `Camel :: YAML DSL :: Deserializers` (5.8s) - `Camel :: Catalog :: Camel Report Maven Plugin` (5.0s) - `Camel :: Catalog :: Camel Route Parser` (5.0s) - `Camel :: JBang :: Plugin :: Testing` (4.0s) - `Camel :: All Components Sync point` (3.0s) - `Camel :: YAML DSL :: Validator Maven Plugin` (2.6s) - `Camel :: Catalog :: Maven` (2.2s) </details> --- :gear: [View full build and test results](https://github.com/apache/camel/actions/runs/38607511621) -- 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]
