Skip to content

fix(uv): keep JDK paths valid during sdist builds #108

fix(uv): keep JDK paths valid during sdist builds

fix(uv): keep JDK paths valid during sdist builds #108

Triggered via pull request July 11, 2026 10:48
Status Failure
Total duration 7m 28s
Artifacts 2

performance-benchmark.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
comment
Unhandled error: HttpError: Resource not accessible by integration
startup
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
analysis
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
comment
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/download-artifact@v4, actions/github-script@v7. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
analysis-benchmark-results
622 Bytes
sha256:2b08b16bb2d1b151a309f2d9291f294ef55e12a26aa6fdc99c65900b14af3764
startup-benchmark-results
830 Bytes
sha256:f56be71028c8c3c37240e3c7d97426490444d8e82dcf43e1064d4bab4eacfbba