Skip to content

[dev/1.3] Disable degraded time index migration IT#18182

Closed
CRZbulabula wants to merge 1 commit into
apache:dev/1.3from
CRZbulabula:codex/disable-degraded-time-index-migration-it-1.3
Closed

[dev/1.3] Disable degraded time index migration IT#18182
CRZbulabula wants to merge 1 commit into
apache:dev/1.3from
CRZbulabula:codex/disable-degraded-time-index-migration-it-1.3

Conversation

@CRZbulabula

Copy link
Copy Markdown
Contributor

Description

This PR temporarily disables IoTDBRegionMigrateNormalIT.migrateRegionWithDegradedTimeIndexTest on dev/1.3.

The test was introduced by #18157. On current dev/1.3, successTest() calls checkClusterStillWritable() after a successful migration. That helper already writes the second row and verifies count = 2. After returning from successTest(), migrateRegionWithDegradedTimeIndexTest still expects count = 1 before doing its own insert, so the test fails deterministically with expected:<1> but was:<2>.

This change only disables the broken IT method on dev/1.3 and does not change runtime behavior.

Verification

  • mvn spotless:apply -pl integration-test -P with-integration-tests
  • mvn test-compile -DskipTests -pl integration-test -P with-integration-tests was attempted but did not reach compilation because 1.3.7-SNAPSHOT IoTDB module artifacts are not available from the configured Maven repositories.

@CRZbulabula CRZbulabula force-pushed the codex/disable-degraded-time-index-migration-it-1.3 branch from b087a75 to 006ef47 Compare July 10, 2026 04:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant