Repository navigation
Failed to install runtime_python_requirements #114924
Description
The runtime-community CI legs in the 8.0 branch are failing with two errors:
chown: changing ownership of '/home/helixbot/.vsts-env/*': Operation not permitted
and
Failed to install runtime_python_requirements
The second one is what's being captured by the CI system, but seems to be a consequence of the first one.
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1017225
Build error leg or test failing: linux-armv6 Release AllSubsets_Mono
Error Message
{
"ErrorMessage" : "Failed to install runtime_python_requirements",
"BuildRetry" : false,
"ExcludeConsoleLog" : false
}- PR: [automated] Merge branch 'release/8.0' => 'release/8.0-staging' #114668
- Queue:
linux-armv6 Release AllSubsets_Mono - Job result: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1017225&view=logs&j=db8e93a1-262e-5037-1aaf-a14621311ed2&t=c2d6c85a-08d6-524c-58e0-6a79597938c0&l=91
- Log file: https://helixr18s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-release-80-3869953c7bbf4c6f9a/Common.Tests/1/console.c97d120f.log?helixlogtype=result
- Output:
+ chown -R helixbot /home/helixbot/.vsts-env
chown: changing ownership of '/home/helixbot/.vsts-env/include/python3.7m': Operation not permitted
chown: changing ownership of '/home/helixbot/.vsts-env/include': Operation not permitted
chown: changing ownership of '/home/helixbot/.vsts-env/lib/python3.7/orig-prefix.txt': Operation not permitted
chown: changing ownership of '/home/helixbot/.vsts-env/lib/python3.7/collections': Operation not permitted
chown: changing ownership of '/home/helixbot/.vsts-env/lib/python3.7/site-packages/wheel-0.40.0.dist-info/INSTALLER': Operation not permitted
chown: changing ownership of '/home/helixbot/.vsts-env/lib/python3.7/site-packages/wheel-0.40.0.dist-info/entry_points.txt': Operation not permitted
chown: changing ownership of '/home/helixbot/.vsts-env/lib/python3.7/site-packages/wheel-0.40.0.dist-info/METADATA': Operation not permitted
...
...
...
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'error'
error: subprocess-exited-with-error
× Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [6 lines of output]
Cargo, the Rust package manager, is not installed or is not on PATH.
This package requires Rust and Cargo to compile extensions. Install it through
the system's package manager or via https://rustup.rs/
Checking for Rust toolchain....
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
Failed to install runtime_python_requirements
+ echo Failed to install runtime_python_requirements
+ exit 1
[END EXECUTION]
Exit Code:1
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1017225
Error message validated: [Failed to install runtime_python_requirements]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 4/22/2025 7:12:44 PM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 0 | 0 |
Activity
dotnet-policy-service commentedon Apr 23, 2025
Tagging subscribers to this area: @akoeplinger, @matouskozak
See info in area-owners.md if you want to be subscribed.
6 remaining items
dotnet-policy-service commentedon Nov 4, 2025
Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.
jakobbotsch commentedon Nov 4, 2025
I believe #121331 was the temporary workaround for this
am11 commentedon Nov 4, 2025
The real error is at the end
psutil could not be installed from sources because gcc is not installed.:@akoeplinger, @chcosta, please add build-base and linux-headers to the list. Isolated repro:
chcosta commentedon Nov 4, 2025
@am11 is #121331 not resolving the problem? The real error is that psutil stopped including 32 bit prebuilts (https://github.com/giampaolo/psutil/blob/master/HISTORY.rst#712) which exposed an issue with the Helix images that was originally implemented because of lack of arm64 support in some python packages. When prebuilts are not found, the package manager tries to build them from source which surfaces as the error you listed. We temporarily pinned to an earlier psutil version which includes the prebuilts and that now necessitates pinning the alpine images so that the psutil version matches. The real fix for this will rollout this week (fingers crossed), and then #121331 will no longer be necessary.
am11 commentedon Nov 4, 2025
@chcosta, yes that downgrade was a workaround and fallback to source build is also known. Seeing that this issue is opened for about seven months, it caught my attention. The fix turned out to be literally one liner:
apk add py3-pip python3-dev build-base linux-headers, which I've shown above.chcosta commentedon Nov 5, 2025
@am11 , sure, i have no opinion on this long standing issue, more specifically, I assumed I was tagged in regards to psutil which does not need additional dependencies. With respect to the rest, I'll peace out :)
JulieLeeMSFT commentedon Jul 10, 2026
Moving to Future as there is a workaround (#121331)
am11 commentedon Jul 10, 2026
It was a one off infra issue. No hits in 30 days, it's safe to close.