Skip to content

Clients should accept messages secured by an expired SecurityToken #381

Clients should accept messages secured by an expired SecurityToken

Clients should accept messages secured by an expired SecurityToken #381

Triggered via pull request November 10, 2024 08:53
Status Success
Total duration 10m 47s
Artifacts

main.yml

on: pull_request
code-coverage  /  cov
2m 22s
code-coverage / cov
verify-clean-address-space  /  address_space
10s
verify-clean-address-space / address_space
verify-clean-node-ids  /  node_ids
5s
verify-clean-node-ids / node_ids
verify-clean-supported-message  /  supported_message
8s
verify-clean-supported-message / supported_message
verify-clean-types  /  types
6s
verify-clean-types / types
verify-code-formatting  /  fmt
11s
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

2 warnings
code-coverage / cov
The following actions uses node12 which is deprecated and will be forced to run on node16: SierraSoftworks/setup-grcov@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
code-coverage / cov
The following actions use a deprecated Node.js version and will be forced to run on node20: SierraSoftworks/setup-grcov@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/