Skip to content
Java CI with Maven

Make configurable the maximum qos that a server can handle #640

Sign in to view logs

Make configurable the maximum qos that a server can handle

Make configurable the maximum qos that a server can handle #640

Triggered via pull request January 22, 2024 16:37
@andselandsel
opened #811
andsel:feature/configurable_max_qos_in_subscription
Status Failure
Total duration 9m 55s
Artifacts –

maven_build.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
Test JDK 17, ubuntu-latest
Process completed with exit code 1.
Test JDK 17, ubuntu-20.04
Process completed with exit code 1.
Test JDK 11, ubuntu-20.04
Process completed with exit code 1.
Test JDK 11, ubuntu-latest
Process completed with exit code 1.
Test JDK 17, ubuntu-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test JDK 17, ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test JDK 11, ubuntu-20.04
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test JDK 11, ubuntu-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/