Skip to content

Implement Custom Bind Address for Port Forwarding #774

Implement Custom Bind Address for Port Forwarding

Implement Custom Bind Address for Port Forwarding #774

Triggered via pull request January 3, 2024 13:49
Status Success
Total duration 3m 11s
Artifacts

test.yaml

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

Annotations

20 errors and 8 warnings
test (3.12, 1.29.0)
Event loop is closed
test (3.12, 1.29.0)
Event loop is closed
test (3.10, 1.27.3)
Event loop is closed
test (3.10, 1.27.3)
Event loop is closed
test (3.9, 1.29.0)
Event loop is closed
test (3.9, 1.29.0)
Event loop is closed
test (3.9, 1.29.0)
Event loop is closed
test (3.8, 1.29.0)
Event loop is closed
test (3.8, 1.29.0)
Event loop is closed
test (3.10, 1.29.0)
Event loop is closed
test (3.10, 1.29.0)
Event loop is closed
test (3.10, 1.28.0)
Event loop is closed
test (3.10, 1.28.0)
Event loop is closed
test (3.10, 1.28.0)
Event loop is closed
test (3.10, 1.28.0)
Event loop is closed
test (3.11, 1.29.0)
Event loop is closed
test (3.11, 1.29.0)
Event loop is closed
test (3.10, 1.26.6)
Event loop is closed
test (3.10, 1.26.6)
Event loop is closed
test (3.10, 1.26.6)
Event loop is closed
test (3.12, 1.29.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (3.10, 1.27.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (3.9, 1.29.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (3.8, 1.29.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (3.10, 1.29.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (3.10, 1.28.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (3.11, 1.29.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (3.10, 1.26.6)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/