Skip to content

Fail with a more explicit error when using workflow init in SpringBoot #762

Fail with a more explicit error when using workflow init in SpringBoot

Fail with a more explicit error when using workflow init in SpringBoot #762

Triggered via pull request October 23, 2024 15:53
Status Failure
Total duration 7m 27s
Billable time 15m
Artifacts

ci.yml

on: pull_request
Unit test with in-memory test service [Edge]
7m 14s
Unit test with in-memory test service [Edge]
Unit test with docker service [JDK8]
6m 28s
Unit test with docker service [JDK8]
Unit test with cloud
11s
Unit test with cloud
Copyright and code format
47s
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)
Copyright and code format
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 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 cloud
⚠️ 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
Unit test with in-memory test service [Edge]
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23