igmp: Full rework, add commands, merge implementations #8404
gpotter2unittests.yml
on: pull_request
Check the validity of the commits
5s
Check SPDX identifiers
7s
Code health check
25s
Build doc
4m 57s
Type hints check
26s
pyca/cryptography test
38s
CodeQL analysis
1m 1s
Matrix: utscapy
Annotations
15 errors and 3 warnings
|
Code health check
Process completed with exit code 1.
|
|
Type hints check
Process completed with exit code 1.
|
|
ubuntu-latest 3.11 non_root -K scanner
Process completed with exit code 1.
|
|
ubuntu-22.04 3.7 non_root -K scanner
Process completed with exit code 1.
|
|
ubuntu-latest 3.10 non_root -K scanner
Process completed with exit code 1.
|
|
ubuntu-latest 3.8 non_root -K scanner
Process completed with exit code 1.
|
|
ubuntu-latest 3.9 non_root -K scanner
Process completed with exit code 1.
|
|
ubuntu-latest 3.13 non_root -K scanner
Process completed with exit code 1.
|
|
ubuntu-latest libpcap 3.14 root -K scanner
Process completed with exit code 1.
|
|
macos-14 3.14 both -K scanner
Process completed with exit code 1.
|
|
ubuntu-latest 3.14 root -K scanner
Process completed with exit code 1.
|
|
ubuntu-latest pypy3.11 root -K scanner
Process completed with exit code 1.
|
|
windows-latest 3.14 root -K scanner
Process completed with exit code 1.
|
|
ubuntu-latest pypy3.11 root -k scanner
Process completed with exit code 1.
|
|
Build doc
Process completed with exit code 1.
|
|
macos-14 3.14 both -k scanner
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
ubuntu-latest 3.14 root -k scanner
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
windows-latest 3.14 both -k scanner
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|