[
https://issues.apache.org/jira/browse/IGNITE-28857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignite TC Bot updated IGNITE-28857:
-----------------------------------
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> Split CDC replication test classes to unlock test parallelization in
> ignite-extensions CI
> -----------------------------------------------------------------------------------------
>
> Key: IGNITE-28857
> URL: https://issues.apache.org/jira/browse/IGNITE-28857
> Project: Ignite
> Issue Type: Task
> Reporter: Anton Vinogradov
> Assignee: Anton Vinogradov
> Priority: Major
>
> RunAllTests wall-clock in the ignite-extensions CI (~46 min) is almost
> entirely defined by the Cdc suite (~41 min). The suite is split into batches
> by the TeamCity Parallel Tests feature, but the split granularity is a test
> class, and three giant parameterized classes dominate the run (timings from a
> recent master run):
> * org.apache.ignite.cdc.kafka.CdcKafkaReplicationAppsTest - 84 tests, ~41 min
> * org.apache.ignite.cdc.kafka.CdcKafkaReplicationTest - 84 tests, ~39 min
> * org.apache.ignite.cdc.CdcIgniteToIgniteReplicationTest - 96 tests, ~25 min
> All three inherit AbstractReplicationTest with a 12-combination parameter
> matrix (clientType x atomicity x mode x backups). Every test takes 20-40 s
> because beforeTest() starts two 2-node clusters with persistence and CDC.
> TeamCity cannot split a single class, so the slowest batch (and the whole
> RunAllTests) takes ~41 min while eight of the thirteen Cdc batches finish in
> ~30 s.
> Split each of the three classes into 4 concrete subclasses, each running a
> single (clientType, atomicity) slice of the matrix:
> * the three classes become abstract *AbstractTest (following the existing
> CdcPostgreSqlReplicationAbstractTest naming),
> * 12 new leaf classes (e.g. CdcKafkaReplicationAppsThinClientAtomicTest)
> declare @Parameterized.Parameters returning their slice.
> No test logic changes, the executed test set is exactly the same. The slowest
> class drops to ~10 min, so the Cdc suite wall-clock is expected to drop from
> ~41 min to ~11 min, and RunAllTests from ~46 min to ~15 min.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)