Skip to content
Continuous Integration

Make sure the Schedule Client has the namespace header injected #1250

Sign in to view logs

Make sure the Schedule Client has the namespace header injected

Make sure the Schedule Client has the namespace header injected #1250

Triggered via pull request March 19, 2025 22:08
@Quinn-With-Two-NsQuinn-With-Two-Ns
synchronize #2452
Quinn-With-Two-Ns:issue-2449
Status Success
Total duration 12m 36s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

ci.yml

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