ci: show environment (pip list) before running tests - #2624
Merged
Conversation
Add a dedicated step to print installed packages before test execution, so CI logs clearly show the environment for debugging non-deterministic CI issues. - olive-test-cpu-template.yaml: split the combined 'Test Olive' step into 'Install test dependencies', 'Show environment (pip list)', and 'Test Olive' steps. - run_test.sh: add clear markers around the existing 'pip list' call so it's easy to spot in the single combined script log. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: c5b90c64-865a-4924-82bd-58d4802ee3ed
Contributor
There was a problem hiding this comment.
Pull request overview
This PR improves CI diagnosability by making the installed Python package set clearly visible in logs before test execution, helping troubleshoot environment/version-related failures in Azure Pipelines and the GPU docker-based test path.
Changes:
- Azure Pipelines CPU template: split the previous combined test step into discrete steps for installing test deps, dumping
pip list, then running tests. - GPU docker test script: added explicit log markers around the existing
pip listoutput to make it easier to locate in logs.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .azure_pipelines/scripts/run_test.sh | Adds clear log delimiters around pip list output in the docker-based test run script. |
| .azure_pipelines/job_templates/olive-test-cpu-template.yaml | Splits install/test into separate steps and adds a dedicated pip list step for improved log visibility in Azure Pipelines. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
shaahji
approved these changes
Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe your changes
CI environment can currently be hard to diagnose because installed package
versions aren't clearly visible before the test run. This adds an explicit
environment-visibility step ahead of test execution:
olive-test-cpu-template.yaml(Azure Pipelines CPU CI, Linux & Windows):split the combined "Test Olive" step into three steps:
Install test dependencies,Show environment (pip list), andTest Olive, so theinstalled package list is visible as its own step in the pipeline UI/logs.
run_test.sh(Linux GPU docker test script): added clear log markersaround the existing
pip listcall (kept as part of the same scriptsince it runs as a single
docker runinvocation) to make the environmentdump easy to find in logs.
GitHub Actions (
test-model-fast.yml) already has an independentpip freezestep, so no change was needed there.Checklist before requesting a review
lintrunner -a(Optional) Issue link