Repository navigation
ci: fix the coverage job (PowerShell pin and stale net10.0 path) - #200
Conversation
7.7.0 is published as a dotnet tool but its linux-x64 runtime package is not on nuget.org, so the unpinned install fails the coverage job before any test runs.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Coverage variation | Report missing for cb8dbc61 |
| Diff coverage | ✅ ∅ diff coverage |
Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (cb8dbc6) Report Missing Report Missing Report Missing Head commit (55007ad) 22624 14382 63.57% Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>
Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#200) 0 0 ∅ (not applicable) Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%
1 Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.
AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.
TIP This summary will be updated as you push new changes.
There was a problem hiding this comment.
Pull Request Overview
✅ No blocking issues noticed
No blocking findings were identified. Workflow behavior should still be validated to confirm the pinned tool is installed and usable before coverage execution.
Test suggestions
- Verify the coverage workflow installs the pinned PowerShell version successfully.
- Verify the coverage job can invoke
pwshafter installation and run the coverage tests.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify the coverage workflow installs the pinned PowerShell version successfully.
2. Verify the coverage job can invoke `pwsh` after installation and run the coverage tests.
TIP Add a Jira or Linear ticket key to the branch or title so the reviewer can check the PR against it. Using another tracker? Tell us.
TIP How was this review? Give us feedback
Run-Coverage.ps1 named bin/Debug/net10.0, so the coverage job failed once the repository moved to net11.0 (the host was never found). It now picks the newest framework folder that holds the host.
The coverage job has been failing for two separate reasons, found one behind the other.
Run-Coverage.ps1failed because it hardcodedbin/Debug/net10.0/for the test host, and the repository targets net11.0 (run 43416727454). It now picks the newestnetX.Yfolder that holds the host. The rule that catches this class of problem in workflows (CI-17) does not scan scripts; that is a gap worth closing separately.CI on this pull request is the proof.