Skip to content

feat: reset mqtt3 client on config change #740

feat: reset mqtt3 client on config change

feat: reset mqtt3 client on config change #740

Triggered via pull request November 8, 2023 22:24
Status Failure
Total duration 3m 17s
Artifacts 1
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

maven.yml

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

Annotations

4 errors and 3 warnings
build (ubuntu-latest)
Process completed with exit code 1.
build (ubuntu-latest)
Process completed with exit code 1.
build (windows-latest)
The operation was canceled.
build (windows-latest)
Process completed with exit code 1.
build (ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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/
build (ubuntu-latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (windows-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@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/

Artifacts

Produced during runtime
Name Size
Failed Test Report Expired
480 KB