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

[serve] Unskipped tests in test_constructor_failure.py & test_ray_client.py #21423

Merged
merged 2 commits into from
Jan 7, 2022

Conversation

czgdp1807
Copy link
Contributor

@czgdp1807 czgdp1807 commented Jan 6, 2022

Why are these changes needed?

These tests pass on my machine. Unskipping them here for CI.

Related issue number

Checks

  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@czgdp1807 czgdp1807 added windows testing topics about testing flaky-test labels Jan 6, 2022
@czgdp1807 czgdp1807 changed the title Unskipped tests in test_constructor_failure.py [serve] Unskipped tests in test_constructor_failure.py & test_ray_client.py Jan 6, 2022
Copy link
Contributor

@shrekris-anyscale shrekris-anyscale left a comment

Choose a reason for hiding this comment

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

Looks good! There's a nit with the linter: https://buildkite.com/ray-project/ray-builders-pr/builds/21943#9cb0ca89-be10-4ac0-b529-2c45a184d5a6/1257

Once that's fixed, this is good to go.

@czgdp1807
Copy link
Contributor Author

N.B. #21422 (comment)

@pcmoritz pcmoritz merged commit 51e4880 into ray-project:master Jan 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing topics about testing windows
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants