-
Notifications
You must be signed in to change notification settings - Fork 35
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
Switch workflows to use new requirements-iree-*.txt files. #813
Conversation
pip install --no-compile -r pytorch-cpu-requirements.txt | ||
pip install -r requirements-iree-unpinned.txt | ||
pip install --no-compile \ | ||
-r sharktank/requirements-tests.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.
As above.
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.
I'm not following here. What change do you want made?
I believe
pip install --no-compile \
-r sharktank/requirements-tests.txt \
-e sharktank/
is sufficient, no need to also install sharktank/requirements.txt
or sharktank/requirements-dev.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.
As commented above with this, this drops installing the dependencies specified in sharktank/requirements-dev.txt
. Just wanted to point out that this is the same here but that might have been a little to short. No change needed.
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!
Progress on #760. We could make the scheduled jobs test both pinned and unpinned versions like on #767.
Cleanup included here:
requirements.txt
in some workflows, instead opting to just install from the more specificsharktank/requirements-tests.txt
I did not test the changes to scheduled workflows. Could do that on request, or just revert if we see issues.