Skip to content

DHCP: Handle option 108 correctly when receiving 0.0.0.0 OFFER (#342) #126

DHCP: Handle option 108 correctly when receiving 0.0.0.0 OFFER (#342)

DHCP: Handle option 108 correctly when receiving 0.0.0.0 OFFER (#342) #126

Triggered via push July 25, 2024 10:51
Status Failure
Total duration 20m 2s
Artifacts

build.yml

on: push
Matrix: ubuntu
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
netbsd
Process completed with exit code 1.
openbsd
Process completed with exit code 1.
freebsd
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
ubuntu (ubuntu-latest)
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/
ubuntu (ubuntu-latest)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ubuntu (ubuntu-22.04)
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/
ubuntu (ubuntu-22.04)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/