Skip to content
Continuous Integration

Add failure_reason to nexus_task_execution_failed #737

Sign in to view logs

Add failure_reason to nexus_task_execution_failed

Add failure_reason to nexus_task_execution_failed #737

Triggered via pull request October 18, 2024 16:06
@Quinn-With-Two-NsQuinn-With-Two-Ns
synchronize #2274
Quinn-With-Two-Ns:issue-2273
Status Success
Total duration 9m 59s
Billable time 18m
Artifacts –

ci.yml

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