Skip to content

New Update-with-Start API #896

New Update-with-Start API

New Update-with-Start API #896

Triggered via pull request November 30, 2024 01:53
Status Failure
Total duration 9m 13s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

ci.yml

on: pull_request
Unit test with in-memory test service [Edge]
6m 2s
Unit test with in-memory test service [Edge]
Unit test with docker service [JDK8]
7m 19s
Unit test with docker service [JDK8]
Unit test with cloud
20s
Unit test with cloud
Copyright and code format
42s
Copyright and code format
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 3 warnings
Unit test with cloud
❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration - https://docs.github.com/rest/checks/runs#create-a-check-run)
Unit test with in-memory test service [Edge]
❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration - https://docs.github.com/rest/checks/runs#create-a-check-run)
Unit test with in-memory test service [Edge]
Process completed with exit code 1.
Unit test with docker service [JDK8]
❌ Failed to create checks using the provided token. (HttpError: Resource not accessible by integration - https://docs.github.com/rest/checks/runs#create-a-check-run)
Unit test with docker service [JDK8]
Process completed with exit code 1.
Unit test with cloud
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23
Unit test with in-memory test service [Edge]
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23
Unit test with docker service [JDK8]
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23