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

[Bug] TestRayServiceInPlaceUpdate is flaky #2620

Merged
merged 2 commits into from
Dec 7, 2024

Conversation

kevin85421
Copy link
Member

@kevin85421 kevin85421 commented Dec 6, 2024

Why are these changes needed?

  1. Increase the timeout from 30m to 60m because the time for a normal run needs around 27 ~ 30m. We should divide these tests into different runners in the future.

  2. Add Eventually to check the request's response. The reason is that Ray Serve initially launches with its default values, which are then overwritten by serveConfigV2.

Related issue number

Closes #2617

Checks

I ran TestRayServiceInPlaceUpdate three times for #2611. It failed the first two times. Additionally, the test failed three times in #2588. Hence, the tests failed 5 times out of 6 runs.

I triggered this PR's CI three times, and all runs passed.

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • This PR is not tested :(

Signed-off-by: kaihsun <[email protected]>
Signed-off-by: kaihsun <[email protected]>
@kevin85421 kevin85421 marked this pull request as ready for review December 6, 2024 19:59
@kevin85421 kevin85421 merged commit d05964c into ray-project:master Dec 7, 2024
23 checks passed
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.

[Bug] TestRayServiceInPlaceUpdate is flaky
2 participants