github-actions[bot] commented on PR #30137:
URL: https://github.com/apache/camel/pull/30137#issuecomment-6919100861

   <!-- ci-tested-modules -->
   :test_tube: **CI tested the following changed modules:**
   
   - `catalog/camel-catalog`
   - `components/camel-test/camel-test-dst`
   - `components/camel-zookeeper-master`
   
   :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 |
   | --- | --- | --- | --- |
   | `components/camel-aws/camel-aws2-kinesis` | 
`KinesisConsumerDstTest.everyRecordIsRoutedOnceByEachConsumerAndAfterItsCheckpoint(Dst)[1]`
 | 1 | DST seed 1 of 
KinesisConsumerDstTest.everyRecordIsRoutedOnceByEachConsumerAndAfterItsCheckpoint
 failed: escape: the code under test reached an escape point the harness does 
not control (strict mode): virtual clock read from a thread outside the 
harness: Camel (camel-43) thread #18 - aws2-kinesis:foo. Fix or avoid it, or 
allow it with @DstInstrument(allowEscapes) when it cannot change the result 
Replay: @DstSeed(1) or -Ddst.seed=1 Trace hash 
72ae42f0126944601ccbd22770e40c6f707308f32fda8419f05240e2eeb846ff, 1374 lines, 
full trace: 
target/dst/KinesisConsumerDstTest.everyRecordIsRoutedOnceByEachConsumerAndAfterItsCheckpoint/seed-1.trace
 Last 40 lines: #1208 t=414911 [aws2-kinesis://dst] ledger routed 
shardId-000000000000/end-shardId-000000000000 #1208 t=414911 
[aws2-kinesis://dst] block 69ms processing of end-shardId-000000000000 #1209 
t=41498
 0 [wakeup] run wake processing of end-shardId-000000000000 #1209 t=414980 
[aws2-kinesis://dst] ledger completed 
shardId-000000000000/end-shardId-000000000000 #1209 t=414980 
[aws2-kinesis://dst] block 12ms GetRecords it-18 #1210 t=414992 [wakeup] run 
wake GetRecords it-18 #1210 t=414992 [aws2-kinesis://dst] ledger 
iteratorExpired shardId-000000000001/it-18 #1210 t=414992 [aws2-kinesis://dst] 
block 78ms GetShardIterator shardId-000000000001 AFTER_SEQUENCE_NUMBER #1211 
t=415067 [operator] run finisher #1212 t=415070 [wakeup] run wake 
GetShardIterator shardId-000000000001 AFTER_SEQUENCE_NUMBER #1212 t=415070 
[aws2-kinesis://dst] fake: iterator it-21 for shardId-000000000001 
AFTER_SEQUENCE_NUMBER at 6 #1212 t=415070 [aws2-kinesis://dst] block 1265ms 
GetRecords it-21 #1213 t=415567 [operator] run finisher #1214 t=416067 
[operator] run finisher #1215 t=416335 [wakeup] run wake GetRecords it-21 #1215 
t=416335 [aws2-kinesis://dst] ledger fetched 
shardId-000000000001/end-shardId-000000000001 
 #1215 t=416335 [aws2-kinesis://dst] fake: GetRecords shardId-000000000001 
returns 1 records from 6 #1215 t=416335 [aws2-kinesis://dst] ledger routed 
shardId-000000000001/end-shardId-000000000001 #1215 t=416335 
[aws2-kinesis://dst] block 69ms processing of end-shardId-000000000001 #1216 
t=416404 [wakeup] run wake processing of end-shardId-000000000001 #1216 
t=416404 [aws2-kinesis://dst] ledger completed 
shardId-000000000001/end-shardId-000000000001 #1217 t=416504 
[aws2-kinesis://dst] run Kinesis2Consumer (periodic) #1217 t=416504 
[aws2-kinesis://dst] block 715ms GetRecords it-20 #1218 t=416567 [operator] run 
finisher #1219 t=417219 [wakeup] run wake GetRecords it-20 #1219 t=417219 
[aws2-kinesis://dst] block 59ms GetRecords it-22 #1220 t=417278 [wakeup] run 
wake GetRecords it-22 #1220 t=417278 [main] check the consumer uses the Kinesis 
API as documented: ok #1220 t=417278 [main] check a consumer routes a record at 
most once, apart from a record after its checkpoint: ok #1220 t=417278 
 [main] check a restarted route resumes after its checkpoint: ok #1220 t=417278 
[main] check every record is routed once the faults cleared, apart from records 
skipped by a LATEST iterator: ok #1220 t=417278 [main] check the checkpoint 
reaches the last record of each open shard once the faults cleared: ok #1220 
t=417278 [main] drop 1 pending tasks #1220 t=417278 [main] wait up to 5000ms 
for result of DefaultShutdownStrategy$ShutdownTask #1221 t=417278 
[ShutdownTask] run DefaultShutdownStrategy$ShutdownTask #1221 t=417278 
[ShutdownTask] shutdown executor Kinesis_shard_monitor #1221 t=417278 
[ShutdownTask] cancel Kinesis2Consumer #1221 t=417278 [ShutdownTask] shutdown 
executor aws2-kinesis://dst #1221 t=417278 [main] shutdown executor 
ShutdownTask #1221 t=417278 [main] FAILED 
org.apache.camel.test.dst.DstViolation: escape: the code under test reached an 
escape point the harness does not control (strict mode): virtual clock read 
from a thread outside the harness: Camel (camel-43) thread
  #18 - aws2-kinesis:foo. Fix or avoid it, or allow it with 
@DstInstrument(allowEscapes) when it cannot change the result |
   
   > :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: 22 of 
726 tested, 3 compile-only — current: 22 all tested</summary>
   
   [Maveniverse Scalpel](https://github.com/maveniverse/scalpel) detected **22 
affected modules** (current approach: 22).
   
   **Skip-tests mode would test 22 modules** (3 direct + 0 downstream), **skip 
tests for 3** (generated code, meta-modules)
   
   <details><summary>Modules Scalpel would test (22)</summary>
   
   - `camel-aws2-eventbridge` ← depends on affected reactor module 
org.apache.camel:camel-aws2-sqs
   - `camel-aws2-kinesis` ← depends on affected reactor module 
org.apache.camel:camel-test-dst
   - `camel-aws2-sqs` ← depends on affected reactor module 
org.apache.camel:camel-test-dst
   - `camel-azure-eventhubs` ← depends on affected reactor module 
org.apache.camel:camel-test-dst
   - `camel-chaos` ← depends on affected reactor module 
org.apache.camel:camel-test-dst
   - `camel-cli-connector` ← depends on affected reactor module 
org.apache.camel:camel-chaos
   - `camel-cli-debug` ← depends on affected reactor module 
org.apache.camel:camel-cli-connector
   - `camel-google-pubsub` ← depends on affected reactor module 
org.apache.camel:camel-test-dst
   - `camel-jbang-mcp` ← depends on affected reactor module 
org.apache.camel:camel-chaos
   - `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-chaos
   - `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-kafka-share` ← depends on affected reactor module 
org.apache.camel:camel-test-dst
   - `camel-launcher-container` ← depends on affected reactor module 
org.apache.camel:camel-launcher
   - `camel-nats` ← depends on affected reactor module 
org.apache.camel:camel-test-dst
   - `camel-pulsar` ← depends on affected reactor module 
org.apache.camel:camel-test-dst
   - `camel-slack` ← depends on affected reactor module 
org.apache.camel:camel-test-dst
   - `camel-test-dst` ← 
components/camel-test/camel-test-dst/src/main/docs/test-dst.adoc
   - `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
   - `camel-zookeeper-master` ← 
components/camel-zookeeper-master/src/generated/resources/META-INF/org/apache/camel/component/zookeepermaster/zookeeper-master.json,
 
components/camel-zookeeper-master/src/test/java/org/apache/camel/component/zookeepermaster/dst/FakeZooKeeper.java,
 
components/camel-zookeeper-master/src/test/java/org/apache/camel/component/zookeepermaster/dst/ZooKeeperMasterDstTest.java,
 
components/camel-zookeeper-master/src/test/java/org/apache/camel/component/zookeepermaster/dst/ZooKeeperMasterWorld.java,
 components/camel-zookeeper-master/src/test/resources/log4j2.properties, own 
pom components/camel-zookeeper-master/pom.xml changed
   
   </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 (49 modules, 8m 24s total)</summary>
   
   **Total reactor time:** 8m 24s
   
   | Module | Duration | Status |
   | --- | --- | --- |
   | Camel :: DSL :: CLI Connector | 57.3s | SUCCESS |
   | Camel :: JBang :: MCP | 49.2s | SUCCESS |
   | Camel :: AWS2 Kinesis | 43.6s | SUCCESS |
   | Camel :: Kafka :: Share | 41.9s | SUCCESS |
   | Camel :: Slack | 40.3s | SUCCESS |
   | Camel :: Component DSL | 39.3s | SUCCESS |
   | Camel :: YAML DSL :: Validator | 23.7s | SUCCESS |
   | Camel :: JBang :: Plugin :: Validate | 23.3s | SUCCESS |
   | Camel :: Docs | 20.6s | SUCCESS |
   | Camel :: JBang :: Run | 18.9s | SUCCESS |
   | Camel :: YAML DSL | 17.1s | SUCCESS |
   | Camel :: Catalog :: Camel Report Maven Plugin | 17.1s | SUCCESS |
   | Camel :: Catalog :: Camel Catalog | 15.4s | SUCCESS |
   | Camel :: JBang :: Plugin :: Kubernetes | 12.6s | SUCCESS |
   | Camel :: JBang :: Plugin :: Testing | 11.5s | SUCCESS |
   | Camel :: AWS2 Eventbridge | 9.4s | SUCCESS |
   | Camel :: Kamelet Main | 9.0s | SUCCESS |
   | Camel :: Test :: DST | 8.6s | SUCCESS |
   | Camel :: JBang :: Plugin :: Generate | 6.5s | SUCCESS |
   | Camel :: Catalog :: Suggest (deprecated) | 4.9s | SUCCESS |
   | Camel :: All Components Sync point | 4.9s | SUCCESS |
   | Camel :: JBang :: Plugin :: MCP | 3.9s | SUCCESS |
   | Camel :: YAML DSL :: Deserializers | 3.5s | SUCCESS |
   | Camel :: Catalog :: Camel Route Parser | 3.4s | SUCCESS |
   | Camel :: YAML DSL :: Validator Maven Plugin | 2.5s | SUCCESS |
   | Camel :: JBang :: Plugin :: Edit | 2.4s | SUCCESS |
   | Camel :: Catalog :: Maven | 2.3s | SUCCESS |
   | Camel :: Endpoint DSL :: Support | 1.7s | SUCCESS |
   | Camel :: Coverage | 1.6s | SUCCESS |
   | Camel :: YAML DSL :: Maven Plugins | 1.6s | SUCCESS |
   | Camel :: DSL :: CLI Debug | 1.4s | SUCCESS |
   | Camel :: Assembly | 1.4s | SUCCESS |
   | Camel :: JBang :: Integration tests | 1.0s | SUCCESS |
   | Camel :: JBang :: Main | 0.7s | SUCCESS |
   | Camel :: Catalog :: Dummy Component | 0.6s | SUCCESS |
   | Camel :: Launcher :: Container | 0.4s | SUCCESS |
   | Camel :: Catalog :: Console | 0.3s | SUCCESS |
   | Camel :: AWS2 SQS | n/a |  |
   | Camel :: Azure :: Event Hubs | n/a |  |
   | Camel :: Chaos | n/a |  |
   | Camel :: Endpoint DSL | n/a |  |
   | Camel :: Google :: PubSub | n/a |  |
   | Camel :: Integration Tests | n/a |  |
   | Camel :: JBang :: Core | n/a |  |
   | Camel :: JBang :: Plugin :: TUI | n/a |  |
   | Camel :: Launcher | n/a |  |
   | Camel :: Nats | n/a |  |
   | Camel :: Pulsar | n/a |  |
   | Camel :: Zookeeper Master | n/a |  |
   
   **Top 20 slowest modules:**
   - `Camel :: DSL :: CLI Connector` (57.3s)
   - `Camel :: JBang :: MCP` (49.2s)
   - `Camel :: AWS2 Kinesis` (43.6s)
   - `Camel :: Kafka :: Share` (41.9s)
   - `Camel :: Slack` (40.3s)
   - `Camel :: Component DSL` (39.3s)
   - `Camel :: YAML DSL :: Validator` (23.7s)
   - `Camel :: JBang :: Plugin :: Validate` (23.3s)
   - `Camel :: Docs` (20.6s)
   - `Camel :: JBang :: Run` (18.9s)
   - `Camel :: YAML DSL` (17.1s)
   - `Camel :: Catalog :: Camel Report Maven Plugin` (17.1s)
   - `Camel :: Catalog :: Camel Catalog` (15.4s)
   - `Camel :: JBang :: Plugin :: Kubernetes` (12.6s)
   - `Camel :: JBang :: Plugin :: Testing` (11.5s)
   - `Camel :: AWS2 Eventbridge` (9.4s)
   - `Camel :: Kamelet Main` (9.0s)
   - `Camel :: Test :: DST` (8.6s)
   - `Camel :: JBang :: Plugin :: Generate` (6.5s)
   - `Camel :: Catalog :: Suggest (deprecated)` (4.9s)
   
   </details>
   
   ---
   :gear: [View full build and test 
results](https://github.com/apache/camel/actions/runs/43858772235)


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