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

[CI] fix virtualenv version to deflake linux:https://python/ray/tests:test_runtime_env_complicated #34650

Merged
merged 3 commits into from
Apr 21, 2023

Conversation

scv119
Copy link
Contributor

@scv119 scv119 commented Apr 21, 2023

Why are these changes needed?

Looks the virtualenv has been upgraded between the success and failed test.

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • 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 added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • 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 :(

@scv119 scv119 marked this pull request as ready for review April 21, 2023 03:52
@scv119 scv119 changed the title [CI] fix virtualenv for runtimeenv test [CI] fix virtualenv version to deflake linux:https://python/ray/tests:test_runtime_env_complicated Apr 21, 2023
Copy link
Contributor

@rickyyx rickyyx left a comment

Choose a reason for hiding this comment

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

Oh wow , nice. Is there a bad version from virtualenv?

Copy link
Contributor

@rkooo567 rkooo567 left a comment

Choose a reason for hiding this comment

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

This means we won’t work with that version of virtualenv? Maybe we should create another issue to fix that?

@@ -18,7 +18,7 @@ pyyaml
aiosignal
frozenlist
requests
virtualenv>=20.0.24
virtualenv>=20.0.24, != 20.21.1
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is it a virtualenv bug? Should we do <20.21.1?

Copy link
Collaborator

Choose a reason for hiding this comment

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

The reasoning is that if it's not their issue then the next virtualenv will also break things.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i've no idea. let's first see if this deflakes it.

@scv119 scv119 merged commit 3e25544 into ray-project:master Apr 21, 2023
scv119 added a commit that referenced this pull request Apr 21, 2023
…runtime_env_complicated (#34650)

Looks the virtualenv has been upgraded between the success and failed test.
elliottower pushed a commit to elliottower/ray that referenced this pull request Apr 22, 2023
…runtime_env_complicated (ray-project#34650)

Looks the virtualenv has been upgraded between the success and failed test.

Signed-off-by: elliottower <[email protected]>
ProjectsByJackHe pushed a commit to ProjectsByJackHe/ray that referenced this pull request May 4, 2023
…runtime_env_complicated (ray-project#34650)

Looks the virtualenv has been upgraded between the success and failed test.

Signed-off-by: Jack He <[email protected]>
architkulkarni pushed a commit to architkulkarni/ray that referenced this pull request May 16, 2023
…runtime_env_complicated (ray-project#34650)

Looks the virtualenv has been upgraded between the success and failed test.
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.

None yet

6 participants