The CI GitHub Action uses make test-requirements, which uses pip-sync, so we should be getting repeatable dependency sets even though our test runners re-use their virtualenvs. However, we've been seeing some cases where tests pass on one PR and then fail on another due to issues related to dependencies.
The CI GitHub Action uses
make test-requirements, which usespip-sync, so we should be getting repeatable dependency sets even though our test runners re-use their virtualenvs. However, we've been seeing some cases where tests pass on one PR and then fail on another due to issues related to dependencies.