Add CI workflow lane for dependency testing (canary lane) - #3430
Add CI workflow lane for dependency testing (canary lane)#3430deruyter92 wants to merge 10 commits into
Conversation
d9ce322 to
a7b8470
Compare
C-Achard
added
dependencies
There was a problem hiding this comment.
Very nice, super useful for the version upgrades milestone.
One higher level design question, would you be in favor of removing those tests once we successfully increment a package and keep the infra for later? Or would this be more of a permanent CI lane by design?
| echo "Force-installing (--no-deps): $pkg" | ||
| python -m pip install --no-cache-dir --upgrade --no-deps "$pkg" |
There was a problem hiding this comment.
Do we want no-deps given that users would most often update their full stack? What do you think would be most useful here?
There was a problem hiding this comment.
yes I was not sure about this one. I would still lean towards keeping --no-deps because it helps us isolate the current issues in specific dependencies (e.g. pandas, numpy, matplotlib, etc).
Maybe after we finish the current round of updating our dependency stack we can change it to a more generic canary lane where the full stack is updated
Co-authored-by: Cyril Achard <cyril.achard@epfl.ch>
Co-authored-by: Cyril Achard <cyril.achard@epfl.ch>
2 participants
Motivation
We currently enforce version pins for quite some dependencies. This PR introduces a non-blocking test lane that can help to identify future-incompatibilities when we release these upper bounds.
Changes
Add add a non-blocking "canary" test lane that tests future compatibility for specific pip-overrides. Currently, we run only the pytests and the torch functional tests for just one python version (3.12) and os (ubuntu). The following dependency overrides are tested:
albumentations >= 2numpy >= 2pandas >= 3matplotlib >= 3.9Related PRs