Skip to content

Clients should accept messages secured by an expired SecurityToken #386

Clients should accept messages secured by an expired SecurityToken

Clients should accept messages secured by an expired SecurityToken #386

Triggered via pull request November 12, 2024 09:45
Status Failure
Total duration 10m 29s
Artifacts

main.yml

on: pull_request
code-coverage  /  cov
1m 51s
code-coverage / cov
verify-clean-address-space  /  address_space
13s
verify-clean-address-space / address_space
verify-clean-node-ids  /  node_ids
7s
verify-clean-node-ids / node_ids
verify-clean-supported-message  /  supported_message
5s
verify-clean-supported-message / supported_message
verify-clean-types  /  types
8s
verify-clean-types / types
verify-code-formatting  /  fmt
10s
verify-code-formatting / fmt
verify-clean-status-codes  /  status_codes
5s
verify-clean-status-codes / status_codes
Matrix: build-linux
Matrix: build-windows
Fit to window
Zoom out
Zoom in

Annotations

7 errors
code-coverage / cov
Process completed with exit code 101.
build-linux (beta)
Process completed with exit code 101.
build-linux (stable)
The job was canceled because "beta" failed.
build-linux (stable)
The operation was canceled.
build-windows (beta)
Process completed with exit code 1.
build-windows (stable)
The job was canceled because "beta" failed.
build-windows (stable)
Process completed with exit code 1.