Skip to content

Do runtime check to ensure update validator has the same parameters as the update it validates #861

Do runtime check to ensure update validator has the same parameters as the update it validates

Do runtime check to ensure update validator has the same parameters as the update it validates #861

Triggered via pull request November 22, 2024 15:42
Status Success
Total duration 35m 54s
Billable time 20m
Artifacts

ci.yml

on: pull_request
Unit test with in-memory test service [Edge]
7m 44s
Unit test with in-memory test service [Edge]
Unit test with docker service [JDK8]
11m 25s
Unit test with docker service [JDK8]
Unit test with cloud
22s
Unit test with cloud
Copyright and code format
55s
Copyright and code format
Fit to window
Zoom out
Zoom in

Annotations

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