-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Clean up ray-ml requirements #23325
Clean up ray-ml requirements #23325
Conversation
# TODO(amogkam): Remove after https://github.com/tensorflow/tensorflow/issues/52922 is fixed. | ||
keras==2.6.0 | ||
tensorflow==2.6.0 | ||
tensorflow~=2.6.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe remove here and only have it only in python/requirements.txt
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anything against allowing tensorflow 2.7 or 2.8 btw? Probably one of the breaking changes in 2.7? Or is it pinned to sync with tensorflow-probability
releases?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually it's a breaking change but cc @sven1977 for more details
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this sync up is necessary indeed. There's a note in their docs:
Note: Since TensorFlow is not included as a dependency of the TensorFlow Probability package (in
setup.py
), you must explicitly install the TensorFlow package (tensorflow
ortensorflow-gpu
). This allows us to maintain one package instead of separate packages for CPU and GPU-enabled TensorFlow.
Which is actually outdated as tensorflow-gpu
is deprecated. They could simply have the correct tensorflow requirement range specified in the probability package requirements, and there would be no need to manually sync up here anymore (i.e. simply only specify tensorflow-probability==XXX
in python/requirements.txt
).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, thank. I'd like to get a quick glance from @sven1977 and @amogkam (and maybe @matthewdeng) to see if they expect any issues with these changes.
|
||
tensorflow~=2.6.2 | ||
tensorflow-probability~=0.14.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is keras installed as a dependency in tensorflow automatically?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
exactly. There was a small problem back in the day (#20032) for a single version, but that's fixed and so tensorflow will request the right version of keras
# TODO(amogkam): Remove after https://github.com/tensorflow/tensorflow/issues/52922 is fixed. | ||
keras==2.6.0 | ||
tensorflow==2.6.0 | ||
tensorflow~=2.6.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually it's a breaking change but cc @sven1977 for more details
It seems
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a bunch for doing this @ddelange!
Just left a couple minor suggestions!
&& $HOME/anaconda3/bin/pip --no-cache-dir install -U -r requirements_ml_docker.txt \ | ||
&& $HOME/anaconda3/bin/pip --no-cache-dir install -U -r requirements_upstream.txt \ | ||
&& $HOME/anaconda3/bin/pip --no-cache-dir install -U pip \ | ||
&& $HOME/anaconda3/bin/pip --no-cache-dir install -U \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice thanks for doing this!
Co-authored-by: Kai Fricke <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Please ping again once CI finishes! Thanks again @ddelange!
@@ -85,7 +85,6 @@ pytest-lazy-fixture | |||
pytest-timeout | |||
pytest-virtualenv | |||
scikit-learn==0.22.2 | |||
tensorflow==2.5.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this change need to be documented anywhere?
I have a feeling that removing |
Can it be that
From
From
|
All tests are now passing except for Windows
@amogkam I see it's the top flakey test for serve, what do you guys usually do in this case? Can you confirm this is indeed flakiness? |
Just reran the test...let's see if it passes this time around. But it does look unrelated to your changes so I think we should be good here! |
@amogkam looks like we're green! |
This is amazing. Thanks! |
In https://github.com/ray-project/ray/blob/ray-1.11.0/docker/ray-ml/Dockerfile, the order of pip install commands currently matters (potentially a lot). It would be good to run one big pip install command to avoid ending up with a broken env. Co-authored-by: Kai Fricke <[email protected]>
* [release tests] Pin gym everywhere (#23349) * [rllib] Pin gym everywhere (#23384) This PR Pins gym in the app config.yaml's for rllib and tune so that release tests are no longer broken by the new gym version. * [RLlib] Pin Gym Everywhere and turn off gpu for recsim tests (#23452) * [ci] Clean up ray-ml requirements (#23325) In https://github.com/ray-project/ray/blob/ray-1.11.0/docker/ray-ml/Dockerfile, the order of pip install commands currently matters (potentially a lot). It would be good to run one big pip install command to avoid ending up with a broken env. Co-authored-by: Kai Fricke <[email protected]> * Fix merge conflict * Also copy requirements_train.txt Co-authored-by: Avnish Narayan <[email protected]> Co-authored-by: ddelange <[email protected]> Co-authored-by: Amog Kamsetty <[email protected]>
Why are these changes needed?
In https://github.com/ray-project/ray/blob/ray-1.11.0/docker/ray-ml/Dockerfile, the order of
pip install
commands currently matters (potentially a lot). It would be good to run one bigpip install
command to avoid ending up with a broken env:Related issue number
Checks
scripts/format.sh
to lint the changes in this PR.