Skip to content
Continuous Integration

New Update-with-Start API #884

Sign in to view logs

New Update-with-Start API

New Update-with-Start API #884

Triggered via pull request November 29, 2024 02:59
@stephanosstephanos
synchronize #2337
stephanos:uws-new-api
Status Failure
Total duration 12m 25s
Billable time 14m
Artifacts –

ci.yml

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

Annotations

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