github-actions[bot] commented on PR #27592: URL: https://github.com/apache/camel/pull/27592#issuecomment-6075311140
<!-- ci-tested-modules --> :test_tube: **CI tested the following changed modules:** - `catalog/camel-catalog` - `components/camel-wasm` - `docs` :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.retryReplaysAnAgentCommandWithoutThePrefix` | 1 | Index 1 out of bounds for length 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 704 tested, 25 compile-only — current: 9 all tested</summary> [Maveniverse Scalpel](https://github.com/maveniverse/scalpel) detected **9 affected modules** (current approach: 9). **Skip-tests mode would test 9 modules** (3 direct + 8 downstream), **skip tests for 25** (generated code, meta-modules) <details><summary>Modules Scalpel would test (9)</summary> - `camel-jbang-mcp` ← downstream of org.apache.camel:camel-catalog - `camel-jbang-plugin-mcp` ← downstream of org.apache.camel:camel-jbang-core - `camel-jbang-plugin-route-parser` ← downstream of org.apache.camel:camel-route-parser - `camel-jbang-plugin-tui` ← downstream of org.apache.camel:camel-catalog - `camel-jbang-plugin-validate` ← downstream of org.apache.camel:camel-yaml-dsl-validator - `camel-launcher-container` ← downstream of org.apache.camel:camel-launcher - `camel-wasm` ← components/camel-wasm/src/main/docs/wasm-language.adoc, components/camel-wasm/src/main/java/org/apache/camel/language/wasm/WasmExpression.java, components/camel-wasm/src/test/java/org/apache/camel/language/wasm/WasmLanguageTest.java - `camel-yaml-dsl-validator` ← downstream of org.apache.camel:camel-catalog - `camel-yaml-dsl-validator-maven-plugin` ← downstream of org.apache.camel:camel-yaml-dsl-validator </details> <details><summary>Modules with tests skipped (25)</summary> - `apache-camel` - `camel-allcomponents` - `camel-catalog-console` - `camel-catalog-maven` - `camel-catalog-suggest` - `camel-componentdsl` - `camel-endpointdsl` - `camel-endpointdsl-support` - `camel-itest` - `camel-jbang-core` - `camel-jbang-it` - `camel-jbang-main` - `camel-jbang-plugin-edit` - `camel-jbang-plugin-generate` - `camel-jbang-plugin-kubernetes` - `camel-jbang-plugin-test` - `camel-kamelet-main` - `camel-launcher` - `camel-report-maven-plugin` - `camel-route-parser` - `camel-yaml-dsl` - `camel-yaml-dsl-deserializers` - `camel-yaml-dsl-maven-plugin` - `coverage` - `dummy-component` </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 (36 modules, 6m 3s total)</summary> **Total reactor time:** 6m 3s | Module | Duration | Status | | --- | --- | --- | | Camel :: Launcher | 53.7s | SUCCESS | | Camel :: JBang :: Plugin :: TUI | 46.2s | SUCCESS | | Camel :: JBang :: MCP | 40.6s | SUCCESS | | Camel :: Catalog :: Camel Catalog | 23.4s | SUCCESS | | Camel :: Component DSL | 20.3s | SUCCESS | | Camel :: YAML DSL :: Validator | 19.2s | SUCCESS | | Camel :: YAML DSL | 18.9s | SUCCESS | | Camel :: JBang :: Plugin :: Validate | 17.2s | SUCCESS | | Camel :: Docs | 15.1s | SUCCESS | | Camel :: JBang :: Plugin :: Testing | 14.8s | SUCCESS | | Camel :: Kamelet Main | 12.9s | SUCCESS | | Camel :: Wasm | 11.4s | SUCCESS | | Camel :: JBang :: Plugin :: Kubernetes | 11.3s | SUCCESS | | Camel :: Catalog :: Camel Route Parser | 8.7s | SUCCESS | | Camel :: YAML DSL :: Deserializers | 8.3s | SUCCESS | | Camel :: Catalog :: Camel Report Maven Plugin | 7.7s | SUCCESS | | Camel :: All Components Sync point | 5.5s | SUCCESS | | Camel :: YAML DSL :: Maven Plugins | 4.2s | SUCCESS | | Camel :: YAML DSL :: Validator Maven Plugin | 4.1s | SUCCESS | | Camel :: Catalog :: Maven | 3.0s | SUCCESS | | Camel :: Catalog :: Suggest (deprecated) | 2.4s | SUCCESS | | Camel :: JBang :: Plugin :: Edit | 1.8s | SUCCESS | | Camel :: Assembly | 1.8s | SUCCESS | | Camel :: Coverage | 1.6s | SUCCESS | | Camel :: Catalog :: Console | 1.4s | SUCCESS | | Camel :: JBang :: Plugin :: Generate | 1.4s | SUCCESS | | Camel :: Catalog :: Dummy Component | 1.2s | SUCCESS | | Camel :: JBang :: Integration tests | 1.2s | SUCCESS | | Camel :: JBang :: Main | 1.1s | SUCCESS | | Camel :: Endpoint DSL :: Support | 0.9s | SUCCESS | | Camel :: Launcher :: Container | 0.7s | SUCCESS | | Camel :: JBang :: Plugin :: MCP | 0.6s | SUCCESS | | Camel :: JBang :: Plugin :: Route Parser | 0.5s | SUCCESS | | Camel :: Endpoint DSL | n/a | | | Camel :: Integration Tests | n/a | | | Camel :: JBang :: Core | n/a | | **Top 20 slowest modules:** - `Camel :: Launcher` (53.7s) - `Camel :: JBang :: Plugin :: TUI` (46.2s) - `Camel :: JBang :: MCP` (40.6s) - `Camel :: Catalog :: Camel Catalog` (23.4s) - `Camel :: Component DSL` (20.3s) - `Camel :: YAML DSL :: Validator` (19.2s) - `Camel :: YAML DSL` (18.9s) - `Camel :: JBang :: Plugin :: Validate` (17.2s) - `Camel :: Docs` (15.1s) - `Camel :: JBang :: Plugin :: Testing` (14.8s) - `Camel :: Kamelet Main` (12.9s) - `Camel :: Wasm` (11.4s) - `Camel :: JBang :: Plugin :: Kubernetes` (11.3s) - `Camel :: Catalog :: Camel Route Parser` (8.7s) - `Camel :: YAML DSL :: Deserializers` (8.3s) - `Camel :: Catalog :: Camel Report Maven Plugin` (7.7s) - `Camel :: All Components Sync point` (5.5s) - `Camel :: YAML DSL :: Maven Plugins` (4.2s) - `Camel :: YAML DSL :: Validator Maven Plugin` (4.1s) - `Camel :: Catalog :: Maven` (3.0s) </details> --- :gear: [View full build and test results](https://github.com/apache/camel/actions/runs/37862986730) -- 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]
