github-actions[bot] commented on PR #28173: URL: https://github.com/apache/camel/pull/28173#issuecomment-6304773709
<!-- ci-tested-modules --> :test_tube: **CI tested the following changed modules:** - `docs` - `dsl/camel-jbang/camel-jbang-plugin-test` - `parent` :white_check_mark: **POM dependency changes: targeted tests included** Changed properties: citrus-version <details><summary>Modules affected by dependency changes (1)</summary> - `:camel-test-citrus` </details> --- <details><summary>:microscope: Scalpel shadow comparison — Scalpel: 9 of 707 tested, 3 compile-only — current: 1 all tested</summary> [Maveniverse Scalpel](https://github.com/maveniverse/scalpel) detected **9 affected modules** (current approach: 1). Changed properties: citrus-version **Skip-tests mode would test 9 modules** (4 direct + 0 downstream), **skip tests for 3** (generated code, meta-modules) <details><summary>:warning: Modules only in Scalpel (8)</summary> - `camel-jbang-mcp` - `camel-jbang-plugin-mcp` - `camel-jbang-plugin-tui` - `camel-jbang-plugin-validate` - `camel-jpa` - `camel-test-citrus` - `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-launcher-container` ← depends on affected reactor module org.apache.camel:camel-launcher - `camel-test-citrus` ← effective dep org.citrusframework:citrus-api, effective dep org.citrusframework:citrus-base, effective dep org.citrusframework:citrus-validation-json, effective dep org.citrusframework:citrus-validation-xml, effective dep org.citrusframework:citrus-validation-text, effective dep org.citrusframework:citrus-validation-yaml - `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> :bulb: **Manual integration tests recommended:** > You modified `dsl/camel-jbang/camel-jbang-plugin-test`. The related integration tests in `dsl/camel-jbang/camel-jbang-it` are excluded from CI. Consider running them manually: > ``` > mvn verify -f dsl/camel-jbang/camel-jbang-it -Djbang-it-test > ``` <details><summary>All tested modules (36 modules, 7m 6s total)</summary> **Total reactor time:** 7m 6s | Module | Duration | Status | | --- | --- | --- | | Camel :: JPA | 57.4s | SUCCESS | | Camel :: Launcher | 53.8s | SUCCESS | | Camel :: JBang :: MCP | 43.1s | SUCCESS | | Camel :: JBang :: Plugin :: Validate | 29.9s | SUCCESS | | Camel :: Test :: Citrus | 29.7s | SUCCESS | | Camel :: YAML DSL | 24.1s | SUCCESS | | Camel :: Catalog :: Camel Catalog | 23.4s | SUCCESS | | Camel :: YAML DSL :: Validator | 23.3s | SUCCESS | | Camel :: Component DSL | 20.1s | SUCCESS | | Camel :: Kamelet Main | 15.2s | SUCCESS | | Camel :: Docs | 14.4s | SUCCESS | | Camel :: JBang :: Plugin :: Kubernetes | 13.5s | SUCCESS | | Camel :: JBang :: Plugin :: Testing | 13.5s | SUCCESS | | Camel :: Catalog :: Camel Report Maven Plugin | 10.2s | SUCCESS | | Camel :: YAML DSL :: Deserializers | 9.6s | SUCCESS | | Camel :: All Components Sync point | 9.6s | SUCCESS | | Camel :: Catalog :: Camel Route Parser | 7.0s | SUCCESS | | Camel :: YAML DSL :: Validator Maven Plugin | 4.8s | SUCCESS | | Camel :: Catalog :: Maven | 3.6s | SUCCESS | | Camel :: YAML DSL :: Maven Plugins | 3.4s | SUCCESS | | Camel :: Catalog :: Suggest (deprecated) | 2.5s | SUCCESS | | Camel :: Coverage | 2.2s | SUCCESS | | Camel :: Assembly | 1.9s | SUCCESS | | Camel :: Catalog :: Dummy Component | 1.7s | SUCCESS | | Camel :: JBang :: Integration tests | 1.3s | SUCCESS | | Camel :: JBang :: Plugin :: Edit | 1.3s | SUCCESS | | Camel :: JBang :: Main | 1.3s | SUCCESS | | Camel :: JBang :: Plugin :: Generate | 1.1s | SUCCESS | | Camel :: Catalog :: Console | 1.1s | SUCCESS | | Camel :: Endpoint DSL :: Support | 0.8s | SUCCESS | | Camel :: JBang :: Plugin :: MCP | 0.6s | SUCCESS | | Camel :: Launcher :: Container | 0.5s | SUCCESS | | Camel :: Endpoint DSL | n/a | | | Camel :: Integration Tests | n/a | | | Camel :: JBang :: Core | n/a | | | Camel :: JBang :: Plugin :: TUI | n/a | | **Top 20 slowest modules:** - `Camel :: JPA` (57.4s) - `Camel :: Launcher` (53.8s) - `Camel :: JBang :: MCP` (43.1s) - `Camel :: JBang :: Plugin :: Validate` (29.9s) - `Camel :: Test :: Citrus` (29.7s) - `Camel :: YAML DSL` (24.1s) - `Camel :: Catalog :: Camel Catalog` (23.4s) - `Camel :: YAML DSL :: Validator` (23.3s) - `Camel :: Component DSL` (20.1s) - `Camel :: Kamelet Main` (15.2s) - `Camel :: Docs` (14.4s) - `Camel :: JBang :: Plugin :: Kubernetes` (13.5s) - `Camel :: JBang :: Plugin :: Testing` (13.5s) - `Camel :: Catalog :: Camel Report Maven Plugin` (10.2s) - `Camel :: YAML DSL :: Deserializers` (9.6s) - `Camel :: All Components Sync point` (9.6s) - `Camel :: Catalog :: Camel Route Parser` (7.0s) - `Camel :: YAML DSL :: Validator Maven Plugin` (4.8s) - `Camel :: Catalog :: Maven` (3.6s) - `Camel :: YAML DSL :: Maven Plugins` (3.4s) </details> --- :gear: [View full build and test results](https://github.com/apache/camel/actions/runs/39503675544) -- 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]
