Skip to content
Build

Used unique port numbers during integration test #2940

Sign in to view logs

Used unique port numbers during integration test

Used unique port numbers during integration test #2940

Triggered via push September 3, 2025 09:31
@Hakky54Hakky54
pushed 4036b7b
master
Status Failure
Total duration 3m 11s
Artifacts –

maven.yml

on: push
code-quality-and-coverage-scan
1m 15s
code-quality-and-coverage-scan
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 3 notices
build (ubuntu-latest, 21)
Process completed with exit code 1.
build (ubuntu-latest, 17)
Process completed with exit code 1.
build (macos-latest, 21)
Process completed with exit code 1.
build (macos-latest, 17)
Process completed with exit code 1.
build (windows-latest, 17)
Process completed with exit code 1.
code-quality-and-coverage-scan
Process completed with exit code 1.
build (windows-latest, 21)
Process completed with exit code 1.
build (windows-latest, 11)
Process completed with exit code 1.
build (windows-latest, 17)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
build (windows-latest, 21)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
build (windows-latest, 11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677