Skip to content
Continuous Integration

Fix - provide default (empty) client config when default user config dir does not exist #2350

Sign in to view logs

Fix - provide default (empty) client config when default user config dir does not exist

Fix - provide default (empty) client config when default user config dir does not exist #2350

Triggered via pull request April 4, 2026 20:53
@THardy98THardy98
opened #2828
fix/envconfig-no-config-dir
Status Success
Total duration 15m 11s
Artifacts –

ci.yml

on: pull_request
Unit test with in-memory test service [Edge]
10m 31s
Unit test with in-memory test service [Edge]
Unit test with docker service [JDK8]
13m 48s
Unit test with docker service [JDK8]
Unit test with cloud
4m 46s
Unit test with cloud
Code format
46s
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