Continuous Integration

workflowcheck - initial support for Java static analyzer #983

Sign in to view logs

Triggered via pull request January 13, 2025 15:26

cretz

synchronize #2356

cretz:workflowcheck

Status Failure

Total duration 10m 56s

Billable time 20m

Artifacts –

ci.yml

on: pull_request

Unit test with in-memory test service [Edge]

Unit test with docker service [JDK8]

Unit test with cloud

Copyright and code format

Annotations

5 errors and 5 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 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 docker service [JDK8]

Process completed with exit code 1.

Unit test with cloud

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Unit test with cloud

⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23

Copyright and code format

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

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