-
Notifications
You must be signed in to change notification settings - Fork 395
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
Update workflow ymls to pin pip-tools to below 6.12.2 #1931
Conversation
3 similar comments
Codecov Report
@@ Coverage Diff @@
## main #1931 +/- ##
==========================================
- Coverage 93.35% 90.72% -2.64%
==========================================
Files 93 46 -47
Lines 4621 1897 -2724
==========================================
- Hits 4314 1721 -2593
+ Misses 307 176 -131
Flags with carried forward coverage won't be shown. Click here to find out more. Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
2 similar comments
* Update CI-python.yml * Update CI-python.yml * Update CI-python.yml * Update CI-python.yml * Update CI-rai_core_flask-pytest.yml * Update CI-e2e-notebooks.yml * Update CI-notebook.yml * Update CI-raiwidgets-pytest.yml Signed-off-by: RubyZ10 <[email protected]>
Description
Looks like pip-tools (6.12.2) had a release today which broke our builds. Looks like it maybe because of the issue jazzband/pip-tools#1804 where you can provide some special paths for requirements and cannot merge two sets of requirements. This PR upper bounds pip-tools in all the yml workflow files where we install pip-tools.
Also, looks like a change in CI-python.yml won't run the python tests due to directory policy. Also, adding another rule when the python tests should run.
Checklist