Skip to content
Continuous Integration

Refactor workflow init validation #836

Sign in to view logs

Refactor workflow init validation

Refactor workflow init validation #836

Re-run triggered November 14, 2024 16:34
@Quinn-With-Two-NsQuinn-With-Two-Ns
#2316
Quinn-With-Two-Ns:refactor-workflow-init
Status Success
Total duration 11m 53s
Billable time 35m
Artifacts –

ci.yml

on: pull_request
Unit test with in-memory test service [Edge]
7m 48s
Unit test with in-memory test service [Edge]
Unit test with docker service [JDK8]
11m 36s
Unit test with docker service [JDK8]
Unit test with cloud
26s
Unit test with cloud
Copyright and code format
38s
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