Summary
The NPU CI Dockerfile heredoc in .buildkite/scripts/hardware_ci/run_npu_test.sh currently installs pytest with:
pip install pytest>=6.0 pytest-cov modelscope
In shell syntax, pytest>=6.0 is parsed as pip install pytest with stdout redirected to a file named =6.0, so the version constraint is not actually applied.
Why this is a bug
- The intended
pytest>=6.0 constraint is silently dropped.
- The build context can get a stray
=6.0 file.
- NPU CI behavior can vary depending on whichever pytest version gets resolved.
Current location
.buildkite/scripts/hardware_ci/run_npu_test.sh:43
Expected fix
Quote the requirement so the shell passes it through literally:
pip install 'pytest>=6.0' pytest-cov modelscope
History
This line was introduced in 2b6d8f17 ([NPU][CI] Add the CI workflow on NPU (#231)) and has not been updated since.
Summary
The NPU CI Dockerfile heredoc in
.buildkite/scripts/hardware_ci/run_npu_test.shcurrently installs pytest with:pip install pytest>=6.0 pytest-cov modelscopeIn shell syntax,
pytest>=6.0is parsed aspip install pytestwith stdout redirected to a file named=6.0, so the version constraint is not actually applied.Why this is a bug
pytest>=6.0constraint is silently dropped.=6.0file.Current location
.buildkite/scripts/hardware_ci/run_npu_test.sh:43Expected fix
Quote the requirement so the shell passes it through literally:
pip install 'pytest>=6.0' pytest-cov modelscopeHistory
This line was introduced in
2b6d8f17([NPU][CI] Add the CI workflow on NPU (#231)) and has not been updated since.