Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPARK-49523][CONNECT] Increase maximum wait time for connect server to come up for testing #47994

Closed
wants to merge 2 commits into from

Conversation

WweiL
Copy link
Contributor

@WweiL WweiL commented Sep 5, 2024

What changes were proposed in this pull request?

This PR increases the max time we wait for a connect server to come up for testing. The current threshold is too low, and is causing flakyness.

Why are the changes needed?

It makes connect tests less flaky.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

It is test infra code.

Was this patch authored or co-authored using generative AI tooling?

No.

Copy link
Member

@HyukjinKwon HyukjinKwon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM we can try

@HyukjinKwon
Copy link
Member

@WweiL mind filing a JIRA please?

Copy link
Contributor

@LuciferYang LuciferYang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, LGTM

@hvanhovell
Copy link
Contributor

Ok, let's get this one merged. I will file the JIRA and update the description.

.build())
.create()

// Execute an RPC which will get retried until the server is up.
assert(spark.version == SparkBuildInfo.spark_version)
eventually(timeout(1.minute)) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Basically this adds another layer of retries. We could also set the maxBackoff to 1 minute.

@hvanhovell hvanhovell changed the title [DO-NOT-MERGE] will it work [SPARK-49523][CONNECT] Increase maximum wait time for connect server to come up for testing Sep 5, 2024
@asfgit asfgit closed this in 182353d Sep 5, 2024
@WweiL
Copy link
Contributor Author

WweiL commented Sep 5, 2024

Oops... thanks guys!

IvanK-db pushed a commit to IvanK-db/spark that referenced this pull request Sep 20, 2024
…to come up for testing

### What changes were proposed in this pull request?
This PR increases the max time we wait for a connect server to come up for testing. The current threshold is too low, and is causing flakyness.

### Why are the changes needed?
It makes connect tests less flaky.

### Does this PR introduce _any_ user-facing change?
No.

### How was this patch tested?
It is test infra code.

### Was this patch authored or co-authored using generative AI tooling?
No.

Closes apache#47994 from WweiL/deflake-will-it-work.

Authored-by: Wei Liu <wei.liu@databricks.com>
Signed-off-by: Herman van Hovell <herman@databricks.com>
attilapiros pushed a commit to attilapiros/spark that referenced this pull request Oct 4, 2024
…to come up for testing

### What changes were proposed in this pull request?
This PR increases the max time we wait for a connect server to come up for testing. The current threshold is too low, and is causing flakyness.

### Why are the changes needed?
It makes connect tests less flaky.

### Does this PR introduce _any_ user-facing change?
No.

### How was this patch tested?
It is test infra code.

### Was this patch authored or co-authored using generative AI tooling?
No.

Closes apache#47994 from WweiL/deflake-will-it-work.

Authored-by: Wei Liu <wei.liu@databricks.com>
Signed-off-by: Herman van Hovell <herman@databricks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants