Anton Vinogradov created IGNITE-28829:
-----------------------------------------
Summary: Split more overloaded test suites to bring RunAll suites
under ~30 minutes
Key: IGNITE-28829
URL: https://issues.apache.org/jira/browse/IGNITE-28829
Project: Ignite
Issue Type: Task
Reporter: Anton Vinogradov
Assignee: Anton Vinogradov
h3. Motivation
Follow-up to IGNITE-28828. After the first split round, a few Java suites still
ran
above ~30 min. This brings the worst remaining splittable ones down by
partitioning
them into balanced halves (by historical per-class runtime).
Test-infrastructure only;
no production code; each split is an exact partition of the original class set.
h3. Change
| Suite | was | new class | after |
| Cache 4 | ~32m | IgniteCacheTestSuite18 | ~16m / ~16m |
| Cache 8 | ~32m | IgniteCacheTestSuite19 | ~15m / ~17m (moves the Eviction
sub-suite + rebalancing tests) |
| Data Structures | ~31m | IgniteCacheDataStructuresSelfTestSuite2 | ~15m /
~15m |
New TeamCity build configs for the new suites must be added to the RunAll chain.
h3. Verified
* ignite-core test sources compile; strict checkstyle (-Pcheckstyle) passes.
* Each split's class set exactly equals the original (no test lost/duplicated).
h3. Deliberately out of scope (single fat test dominates -> splitting won't
help; needs test optimization, separate tickets)
* Disk Page Compressions 4 (~37m one class), Disk Page Compressions 1 (~23m one
class),
Snapshots 4 (~26m one class).
* Cache 3 wraps IgniteCacheTestSuite3.suite() (structural) — needs a different
approach.
* PDS (Indexing) can be split CI-only (its two sub-suites into separate
configs, no code).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
