Replace cluster start integration test - #919
Closed
hectorcast-db wants to merge 1 commit into
Closed
hectorcast-db wants to merge 1 commit into
hectorcast-db wants to merge 1 commit into
Conversation
Signed-off-by: Hector Castejon Diaz <hector.castejon@databricks.com>
Contributor
|
Please ensure that the NEXT_CHANGELOG.md file is updated with any relevant changes. |
Contributor
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
hectorcast-db
added
the
CI:run-diffviewer
hectorcast-db
requested review from
Divyansh-db
and removed request for
Divyansh-db
September 15, 2026 08:33
Contributor
Author
|
PR created in fork by mistake. |
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
1 participant
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.
Changes
ClustersIT.ensuresClusterIsRunning, which starts a real clusterTERMINATED -> start -> PENDING -> RUNNINGinClustersExtTestwith a mockedClustersServiceTests
JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64 mvn spotless:applyJAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64 mvn -pl databricks-sdk-java -Dtest=ClustersExtTest test