Skip to content

Check update validator has a matching update method #846

Check update validator has a matching update method

Check update validator has a matching update method #846

Triggered via pull request November 18, 2024 18:31
Status Failure
Total duration 7m 7s
Billable time 13m
Artifacts

ci.yml

on: pull_request
Unit test with in-memory test service [Edge]
5m 17s
Unit test with in-memory test service [Edge]
Unit test with docker service [JDK8]
6m 58s
Unit test with docker service [JDK8]
Unit test with cloud
13s
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)
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