github-actions[bot] commented on PR #29186: URL: https://github.com/apache/camel/pull/29186#issuecomment-6637066968
<!-- ci-tested-modules --> :test_tube: **CI tested the following changed modules:** - `components/camel-ai/camel-mcp-server` :repeat: **1 test passed only after a retry on JDK 21** (1 retried attempt) <details><summary>Recovered flaky tests on JDK 21 (1)</summary> | Module | Test | Failed attempts | First failure | | --- | --- | --- | --- | | `dsl/camel-jbang/camel-jbang-plugin-tui` | `LaunchManagerOutcomeTest.startedWhenTheStatusFileSaysSo` | 1 | expected: null but was: LaunchOutcome[ok=false, log=null] | > :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 713 tested, 3 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** (1 direct + 0 downstream), **skip tests for 3** (generated code, meta-modules) <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-jbang-core - `camel-jbang-plugin-validate` ← depends on affected reactor module org.apache.camel:camel-jbang-core - `camel-jbang-run` ← depends on affected reactor module org.apache.camel:camel-catalog - `camel-launcher-container` ← depends on affected reactor module org.apache.camel:camel-launcher - `camel-mcp-server` ← components/camel-ai/camel-mcp-server/src/test/java/org/apache/camel/component/mcp/server/vertx/integration/OfficialMcpConformanceIT.java, components/camel-ai/camel-mcp-server/src/test/resources/expected-failures.yaml, components/camel-ai/camel-mcp-server/test-execution.md, own pom components/camel-ai/camel-mcp-server/pom.xml changed - `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> :warning: **Some tests are disabled on GitHub Actions** (`@DisabledIfSystemProperty(named = "ci.env.name")`) and require manual verification: - `components/camel-ai/camel-mcp-server`: 1 test(s) disabled on GitHub Actions <details><summary>All tested modules (36 modules, 5m 24s total)</summary> **Total reactor time:** 5m 24s | Module | Duration | Status | | --- | --- | --- | | Camel :: AI :: MCP Server | 56.7s | SUCCESS | | Camel :: JBang :: MCP | 46.7s | SUCCESS | | Camel :: JBang :: Plugin :: Validate | 26.4s | SUCCESS | | Camel :: YAML DSL :: Validator | 21.8s | SUCCESS | | Camel :: YAML DSL | 19.8s | SUCCESS | | Camel :: JBang :: Run | 19.6s | SUCCESS | | Camel :: Catalog :: Camel Catalog | 18.7s | SUCCESS | | Camel :: Component DSL | 15.6s | SUCCESS | | Camel :: JBang :: Plugin :: Kubernetes | 11.9s | SUCCESS | | Camel :: Docs | 11.8s | SUCCESS | | Camel :: Kamelet Main | 10.7s | SUCCESS | | Camel :: JBang :: Plugin :: Testing | 9.7s | SUCCESS | | Camel :: YAML DSL :: Deserializers | 7.3s | SUCCESS | | Camel :: YAML DSL :: Validator Maven Plugin | 7.1s | SUCCESS | | Camel :: Catalog :: Camel Route Parser | 6.6s | SUCCESS | | Camel :: Catalog :: Camel Report Maven Plugin | 5.9s | SUCCESS | | Camel :: JBang :: Plugin :: Generate | 4.9s | SUCCESS | | Camel :: All Components Sync point | 4.7s | SUCCESS | | Camel :: Assembly | 3.2s | SUCCESS | | Camel :: YAML DSL :: Maven Plugins | 2.8s | SUCCESS | | Camel :: Catalog :: Maven | 2.2s | SUCCESS | | Camel :: Catalog :: Suggest (deprecated) | 1.6s | SUCCESS | | Camel :: Catalog :: Dummy Component | 1.5s | SUCCESS | | Camel :: Coverage | 1.1s | SUCCESS | | Camel :: JBang :: Plugin :: MCP | 1.0s | SUCCESS | | Camel :: Catalog :: Console | 1.0s | SUCCESS | | Camel :: JBang :: Plugin :: Edit | 0.8s | SUCCESS | | Camel :: JBang :: Main | 0.7s | SUCCESS | | Camel :: Endpoint DSL :: Support | 0.7s | SUCCESS | | Camel :: Launcher :: Container | 0.6s | SUCCESS | | Camel :: JBang :: Integration tests | 0.6s | SUCCESS | | Camel :: Endpoint DSL | n/a | | | Camel :: Integration Tests | n/a | | | Camel :: JBang :: Core | n/a | | | Camel :: JBang :: Plugin :: TUI | n/a | | | Camel :: Launcher | n/a | | **Top 20 slowest modules:** - `Camel :: AI :: MCP Server` (56.7s) - `Camel :: JBang :: MCP` (46.7s) - `Camel :: JBang :: Plugin :: Validate` (26.4s) - `Camel :: YAML DSL :: Validator` (21.8s) - `Camel :: YAML DSL` (19.8s) - `Camel :: JBang :: Run` (19.6s) - `Camel :: Catalog :: Camel Catalog` (18.7s) - `Camel :: Component DSL` (15.6s) - `Camel :: JBang :: Plugin :: Kubernetes` (11.9s) - `Camel :: Docs` (11.8s) - `Camel :: Kamelet Main` (10.7s) - `Camel :: JBang :: Plugin :: Testing` (9.7s) - `Camel :: YAML DSL :: Deserializers` (7.3s) - `Camel :: YAML DSL :: Validator Maven Plugin` (7.1s) - `Camel :: Catalog :: Camel Route Parser` (6.6s) - `Camel :: Catalog :: Camel Report Maven Plugin` (5.9s) - `Camel :: JBang :: Plugin :: Generate` (4.9s) - `Camel :: All Components Sync point` (4.7s) - `Camel :: Assembly` (3.2s) - `Camel :: YAML DSL :: Maven Plugins` (2.8s) </details> --- :gear: [View full build and test results](https://github.com/apache/camel/actions/runs/41870408941) -- 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]
