Skip to content

refactor: introduce the packetmuxer layer (#49) #168

refactor: introduce the packetmuxer layer (#49)

refactor: introduce the packetmuxer layer (#49) #168

Triggered via push January 15, 2024 13:39
Status Success
Total duration 46s
Artifacts

build.yml

on: push
short-tests
29s
short-tests
gosec
36s
gosec
coverage-threshold
28s
coverage-threshold
integration
35s
integration
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
coverage-threshold
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
short-tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
integration
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
gosec
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/