Skip to content

Fix parsing of Keycloak-related client configuration options #140

Fix parsing of Keycloak-related client configuration options

Fix parsing of Keycloak-related client configuration options #140

Re-run triggered July 8, 2024 13:02
Status Failure
Total duration 6h 0m 28s
Artifacts

main.yml

on: pull_request
Matrix: build-and-test
Fit to window
Zoom out
Zoom in

Annotations

21 errors
build-and-test (windows-latest, 3.10)
Process completed with exit code 1.
build-and-test (windows-latest, 3.10)
Process completed with exit code -1073741571.
build-and-test (ubuntu-latest, 3.11)
The hosted runner: GitHub Actions 19 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
build-and-test (ubuntu-latest, 3.11)
Process completed with exit code 1.
build-and-test (ubuntu-latest, 3.12)
The hosted runner: GitHub Actions 24 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
build-and-test (ubuntu-latest, 3.12)
Process completed with exit code 1.
build-and-test (ubuntu-latest, 3.9)
The hosted runner: GitHub Actions 32 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
build-and-test (ubuntu-latest, 3.9)
Process completed with exit code 1.
build-and-test (ubuntu-latest, 3.8)
The hosted runner: GitHub Actions 41 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
build-and-test (ubuntu-latest, 3.8)
Process completed with exit code 1.
build-and-test (ubuntu-latest, 3.10)
The hosted runner: GitHub Actions 60 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
build-and-test (ubuntu-latest, 3.10)
Process completed with exit code 1.
build-and-test (windows-latest, 3.12)
The hosted runner: GitHub Actions 57 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
build-and-test (windows-latest, 3.12)
Process completed with exit code 1.
build-and-test (windows-latest, 3.9)
The hosted runner: GitHub Actions 36 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
build-and-test (windows-latest, 3.9)
Process completed with exit code 1.
build-and-test (windows-latest, 3.8)
The hosted runner: GitHub Actions 28 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
build-and-test (windows-latest, 3.8)
Process completed with exit code 1.
build-and-test (windows-latest, 3.11)
The job running on runner GitHub Actions 1 has exceeded the maximum execution time of 360 minutes.
build-and-test (windows-latest, 3.11)
Process completed with exit code 1.
build-and-test (windows-latest, 3.11)
The operation was canceled.