Skip to content

Pin actions/upload-code-coverage action to 82c7aee #211

Pin actions/upload-code-coverage action to 82c7aee

Pin actions/upload-code-coverage action to 82c7aee #211

Triggered via pull request July 2, 2026 14:54
Status Failure
Total duration 1m 31s
Artifacts

test.yml

on: pull_request
Matrix: run
Fit to window
Zoom out
Zoom in

Annotations

44 errors, 66 warnings, and 6 notices
Node.js 16 @ ubuntu-latest
Process completed with exit code 1.
Node.js 16 @ ubuntu-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 24 @ ubuntu-latest
Process completed with exit code 1.
Node.js 24 @ ubuntu-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 18 @ ubuntu-latest
Process completed with exit code 1.
Node.js 18 @ ubuntu-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 20 @ ubuntu-latest
Process completed with exit code 1.
Node.js 20 @ ubuntu-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 12 @ ubuntu-latest
Process completed with exit code 1.
Node.js 12 @ ubuntu-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 14 @ ubuntu-latest
Process completed with exit code 1.
Node.js 14 @ ubuntu-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 22 @ ubuntu-latest
Process completed with exit code 1.
Node.js 22 @ ubuntu-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 16 @ macos-latest
Process completed with exit code 1.
Node.js 16 @ macos-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 18 @ macos-latest
Process completed with exit code 1.
Node.js 18 @ macos-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 25 @ ubuntu-latest
Process completed with exit code 1.
Node.js 25 @ ubuntu-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 24 @ macos-latest
Process completed with exit code 1.
Node.js 24 @ macos-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 20 @ macos-latest
Process completed with exit code 1.
Node.js 20 @ macos-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 16 @ windows-latest
Process completed with exit code 1.
Node.js 16 @ windows-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 24 @ windows-latest
Process completed with exit code 1.
Node.js 24 @ windows-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 25 @ macos-latest
Process completed with exit code 1.
Node.js 25 @ macos-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 18 @ windows-latest
Process completed with exit code 1.
Node.js 18 @ windows-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 22 @ macos-latest
Process completed with exit code 1.
Node.js 22 @ macos-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 20 @ windows-latest
Process completed with exit code 1.
Node.js 20 @ windows-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 22 @ windows-latest
Process completed with exit code 1.
Node.js 22 @ windows-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 25 @ windows-latest
Process completed with exit code 1.
Node.js 25 @ windows-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 14 @ windows-latest
Process completed with exit code 1.
Node.js 14 @ windows-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 12 @ windows-latest
Process completed with exit code 1.
Node.js 12 @ windows-latest
Coverage upload failed (HTTP 403): Resource not accessible by integration. To treat upload errors as warnings, add 'fail-on-error: false' to the action inputs.
Node.js 16 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 16 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 16 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 24 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 24 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 24 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 18 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 18 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 18 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 20 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 20 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 20 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 12 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 12 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 12 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 14 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 14 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 14 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 22 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 22 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 22 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 16 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 16 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 16 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 18 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 18 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 18 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 25 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 25 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 25 @ ubuntu-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 24 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 24 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 24 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 20 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 20 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 20 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 16 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 16 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 16 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 24 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 24 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 24 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 25 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 25 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 25 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 18 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 18 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 18 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 22 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 22 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 22 @ macos-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 20 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 20 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 20 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 22 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 22 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 22 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 25 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 25 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 25 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 14 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 14 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 14 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 12 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 12 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 12 @ windows-latest
Failed to send status report: HTTP Error 403: Forbidden
Node.js 16 @ macos-latest
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
Node.js 18 @ macos-latest
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
Node.js 24 @ macos-latest
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
Node.js 20 @ macos-latest
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
Node.js 25 @ macos-latest
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167
Node.js 22 @ macos-latest
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167