Skip to content
Continuous Integration

Fix flaky MetricsTest by using polling assertions #2045

Sign in to view logs

Fix flaky MetricsTest by using polling assertions

Fix flaky MetricsTest by using polling assertions #2045

Triggered via pull request January 7, 2026 01:46
@mfateevmfateev
opened #2756
mfateev:task/metricstest-flake
Status Failure
Total duration 13m 58s
Artifacts –

ci.yml

on: pull_request
Unit test with in-memory test service [Edge]
7m 18s
Unit test with in-memory test service [Edge]
Unit test with docker service [JDK8]
11m 59s
Unit test with docker service [JDK8]
Unit test with cloud
22s
Unit test with cloud
Code format
46s
Code format
Matrix: Build native test server / Build native test server
Fit to window
Zoom out
Zoom in

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)
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 in-memory test service [Edge]
Process completed with exit code 1.
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