Skip to content
Continuous Integration

💥 Standalone Activities for Java #2552

Sign in to view logs

💥 Standalone Activities for Java

💥 Standalone Activities for Java #2552

Triggered via pull request April 29, 2026 14:05
@GregoryTravisGregoryTravis
synchronize #2858
gmt/java-standalone-activities
Status Failure
Total duration 14m 5s
Artifacts –

ci.yml

on: pull_request
Unit test with in-memory test service [Edge]
12m 24s
Unit test with in-memory test service [Edge]
Unit test with docker service [JDK8]
9m 45s
Unit test with docker service [JDK8]
Unit test with cloud
4m 58s
Unit test with cloud
Code format
57s
Code format
Javadoc
3m 4s
Javadoc
Matrix: Build native test server / Build native test server
Fit to window
Zoom out
Zoom in

Annotations

4 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 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 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 cloud
⚠️ 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
Unit test with in-memory test service [Edge]
⚠️ This usually indicates insufficient permissions. More details: https://github.com/mikepenz/action-junit-report/issues/23