Skip to content
Continuous Integration

Add high-level workflow describe #867

Sign in to view logs

Add high-level workflow describe

Add high-level workflow describe #867

Triggered via pull request November 25, 2024 23:30
@Quinn-With-Two-NsQuinn-With-Two-Ns
synchronize #2326
Quinn-With-Two-Ns:issue-2265
Status Success
Total duration 12m 0s
Billable time 21m
Artifacts –

ci.yml

on: pull_request
Unit test with in-memory test service [Edge]
8m 32s
Unit test with in-memory test service [Edge]
Unit test with docker service [JDK8]
11m 49s
Unit test with docker service [JDK8]
Unit test with cloud
12s
Unit test with cloud
Copyright and code format
49s
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