Skip to content
Continuous Integration

Update-with-Start operation #646

Sign in to view logs

Update-with-Start operation

Update-with-Start operation #646

Triggered via pull request September 24, 2024 17:42
@stephanosstephanos
synchronize #2199
stephanos:update-with-start-op
Status Failure
Total duration 9m 49s
Billable time 18m
Artifacts –

ci.yml

on: pull_request
Unit test with in-memory test service [Edge]
7m 27s
Unit test with in-memory test service [Edge]
Unit test with docker service [JDK8]
9m 35s
Unit test with docker service [JDK8]
Unit test with cloud
15s
Unit test with cloud
Copyright and code format
35s
Copyright and code format
Fit to window
Zoom out
Zoom in

Annotations

4 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 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