microsoft / microsoft/winget-cli
Build Pipeline occasionally errors on component governance with ENOSPC
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Relevant area(s)
WinGet CLI
Relevant command(s)
No response
Brief description of your issue
The Build Pipeline occasionally errors on component governance with ENOSPC. This error does not cause a failure in the build, at least during the component governance stage. It does not affect all PRs and seems to be somewhat random.
Steps to reproduce
Submit a PR and pray you see the defect
Expected behavior
There is sufficient space on the agent or VM to run without errors
Actual behavior
- https://dev.azure.com/shine-oss/winget-cli/_build/results?buildId=196599&view=results
- https://dev.azure.com/shine-oss/winget-cli/_build/results?buildId=194765&view=results
- https://dev.azure.com/shine-oss/winget-cli/_build/results?buildId=191581&view=results
Environment
CLI Build_Test Pipeline
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CLI Build_Test Pipeline and compare the three linked Azure build results, focusing on the component governance stage and the ENOSPC reports. Identify the agent or VM space condition involved and verify the pipeline completes that stage without the intermittent error while preserving the existing non-failing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- build-system, ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100