Continuous Integration

CaN USE_RAMPING_VERSION versioning behaviour (#2868) #2584

Sign in to view logs

Triggered via push May 4, 2026 16:06

maciejdudko

master

Status Failure

Total duration 15m 42s

Artifacts –

ci.yml

on: push

Unit test with in-memory test service [Edge]

Unit test with docker service [JDK8]

Unit test with cloud

Matrix: Build native test server / Build native test server

Annotations

5 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)

Build native test server / Build native test server (ubuntu-latest, linux, amd64, false)

Process completed with exit code 1.

Build native test server / Build native test server (ubuntu-24.04-arm, linux, arm64)

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 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