Skip to content
CI

fallback to ipv4/ipv6 in the event of an unreachable host error #133

Sign in to view logs

fallback to ipv4/ipv6 in the event of an unreachable host error

fallback to ipv4/ipv6 in the event of an unreachable host error #133

Triggered via pull request October 16, 2024 19:19
@GazlerGazler
opened #101
Gazler:gr-httpc-fallback
Status Success
Total duration 2m 37s
Artifacts –

main.yml

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

Annotations

4 warnings
test (1.14, 25, lint)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@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 (1.14, 25, lint)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (1.11, 22)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@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 (1.11, 22)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/