Add openvino-nightly to automated tests #506
Conversation
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
helena-intel
force-pushed
the
helena/test-openvino-nightly
branch
from
acee0e5 to
52a5aae
Compare
helena-intel
force-pushed
the
helena/test-openvino-nightly
branch
from
61a9fa6 to
1aafa43
Compare
| @@ -33,12 +34,9 @@ jobs: | |||
| # install PyTorch CPU version to avoid installing CUDA packages on GitHub runner without GPU | |||
| pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cpu | |||
| pip install .[openvino,nncf,tests,diffusers] | |||
| - name: Install openvino-nightly (optional) | |||
There was a problem hiding this comment.
It make sense to have tests with openvino-nightly, could make sense to add it in the nightly tests instead, wdyt ?
There was a problem hiding this comment.
@echarlaix I think that for now it would be useful to have it here, so we can test the PRs that target 2023.3. And then after 2023.3 we can move this to nightly tests?
There was a problem hiding this comment.
Yes the only issue is that the CI will be red until the next release (as the quantization tests will fail for one at least of the openvino version), will merge it anyway if that helps on your side!
Add openvino-nightly to automated tests (in addition to the openvino that is installed by setup.py).
We may not want to keep this for all the tests forever since it doubles the amount of tests on every PR - but for now it would be useful to check PRs with openvino-nightly before the OpenVINO 2023.0 release, and to catch any issues with openvino-nightly in existing code.
Also changed Python versions to test to 3.8 and 3.11.