Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Recent master CI logs show
IoTDBAlterTimeSeriesTypeIT.testWriteAndAltertaking 213 seconds andIoTDBSessionSchemaTemplateITtaking 217 seconds in Cluster IT - 1C3D. The table-modeltestWriteAndAltertakes 85 seconds in Table Cluster IT - 1C3D.Validation
mvn -o -pl integration-test -P with-integration-tests spotless:applypassed.mvn -o -pl integration-test -P with-integration-tests test-compile -DskipTestspassed, including Checkstyle and Spotless checks.IoTDBAlterTimeSeriesTypeIT#testWriteAndAlterand all 14IoTDBSessionSchemaTemplateITtests passed locally (Memory and PBTree). The Session template class completed in 28.9 seconds on the local Windows 1C1D environment; the CI observations above use different runners/topologies.IoTDBAlterColumnTypeIT#testWriteAndAlterpassed locally.IoTDBPipeClusterIT#testMachineDowntimeAsync+testMachineDowntimeSynccases. The local Windows machine exhausted its commit memory during JVM startup, so this run could not complete; these cases still need CI validation.This PR has: