Skip to content

Update PotentialDeadlockException to account for scheduling delay (#2… #3044

Update PotentialDeadlockException to account for scheduling delay (#2…

Update PotentialDeadlockException to account for scheduling delay (#2… #3044

Triggered via push July 24, 2026 19:15
Status Failure
Total duration 39m 14s
Artifacts

ci.yml

on: push
Unit test with in-memory test service [Edge]
7m 45s
Unit test with in-memory test service [Edge]
Unit test with CLI
16m 35s
Unit test with CLI
Unit test with cloud
5m 36s
Unit test with cloud
Code format
2m 5s
Code format
Javadoc
3m 59s
Javadoc
Matrix: Build native test server / Build native test server
Fit to window
Zoom out
Zoom in

Annotations

4 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 CLI
❌ 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 CLI
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23