Skip to content
Continuous Integration

Add upgrade-on-CAN support #2276

Sign in to view logs

Add upgrade-on-CAN support

Add upgrade-on-CAN support #2276

Triggered via pull request March 19, 2026 21:26
@THardy98THardy98
synchronize #2811
pr/upgrade-on-can
Status Success
Total duration 16m 41s
Artifacts –

ci.yml

on: pull_request
Unit test with in-memory test service [Edge]
9m 34s
Unit test with in-memory test service [Edge]
Unit test with docker service [JDK8]
15m 30s
Unit test with docker service [JDK8]
Unit test with cloud
4m 37s
Unit test with cloud
Code format
48s
Code format
Matrix: Build native test server / Build native test server
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