anton-vinogradov opened a new pull request, #13294: URL: https://github.com/apache/ignite/pull/13294
[IGNITE-28834](https://issues.apache.org/jira/browse/IGNITE-28834) Wrap the load loops / time-boxed durations of the heaviest tests that were not honoring `TEST_SCALE_FACTOR` in `GridTestUtils.SF.applyLB(...)`, so they scale down on CI (where the factor is `0.1`) while keeping a safe lower bound at full scale. ### Scaled tests - `IgniteTxCacheWriteSynchronizationModesMultithreadedTest` — 10s load window - `TxDeadlockDetectionNoHangsTest` / `TxDeadlockDetectionTest` — 2-min run window - `IgniteCacheGetRestartTest` — `TEST_TIME` / `KEYS` - `CrossCacheTxRandomOperationsTest` — 10s window - `SegmentedRingByteBufferTest` — 60s producer/consumer windows - `TxPartitionCounterStateConsistencyTest` — 30s restart windows - `IgnitePdsTransactionsHangTest` — `DURATION` (kept above warm-up) - `CacheFreeListSelfTest` — grow/shrink load (200k → LB 50k) - `ConcurrentCheckpointAndUpdateTtlTest` — checkpoint loop - `IgniteCachePutAllRestartTest` — 2-min + 60s put windows Lower bounds keep each scenario meaningful at factor `0.1` (e.g. ≥20s for deadlock detection, ≥10s for tx/restart windows, ≥50k entries for free-list grow/shrink). Selection stopped where per-test saving drops below ~1 minute; the remaining heavy tests are topology/fan-out bound (no scalable load) and are out of scope. ### Validation `mvn clean test-compile -pl modules/core` is green (JDK 17). 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
