Skip to content
Continuous Integration

SDKTestWorkflowRule wasn't calling shutdown #663

Sign in to view logs

SDKTestWorkflowRule wasn't calling shutdown

SDKTestWorkflowRule wasn't calling shutdown #663

Triggered via pull request September 28, 2024 04:39
@mfateevmfateev
opened #2243
mfateev:unit-test-fix
Status Success
Total duration 9m 42s
Billable time 18m
Artifacts –

ci.yml

on: pull_request
Unit test with in-memory test service [Edge]
7m 3s
Unit test with in-memory test service [Edge]
Unit test with docker service [JDK8]
9m 30s
Unit test with docker service [JDK8]
Unit test with cloud
10s
Unit test with cloud
Copyright and code format
42s
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