CI/CD - Fix Azure test pipeline #754
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #754 +/- ##
=======================================
Coverage 85.71% 85.71%
=======================================
Files 102 102
Lines 7678 7678
=======================================
Hits 6581 6581
Misses 1097 1097
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull Request Overview
This PR adds the --no-build-isolation flag to pip install commands in Azure Pipeline configurations to prevent pip from creating isolated build environments during package installation.
Key changes:
- Added
--no-build-isolationflag to pip install commands in both CPU and CUDA test pipelines - Ensures setuptools is explicitly installed for Python 3.11+ in the CPU test pipeline
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .azure-pipelines/cuda-unit-test.yml | Added --no-build-isolation flag to pip install command for CUDA worker dependencies |
| .azure-pipelines/cpu-unit-test.yml | Added --no-build-isolation flag and explicit setuptools installation for CPU worker dependencies |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
@copilot revise the PR title accordingly |
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Python3.10 verification pipeline failed for conflict 'setuptools' version as below.
Root Cause:
The problem is that modern pip (25.3) uses an isolated build environment with the latest setuptools by default. The pipeline installs setuptools 65.7 in the user environment, but pip builds the package in an isolated environment with newer setuptools, which conflicts with the version check in [setup.py].
Solution:
Remove pip upgrade.