Add support for esp32 network driver scanning for access points #6710
UncleGrumpyAnnotations
56 errors and 76 warnings
|
build-and-test (gcc-13, -O3, 27, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (gcc-9, -O3, 25, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (gcc-11, -O3, 27, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (gcc-13, -O3, 25, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-10, -O3, 26, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-10, -O3, 25, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (gcc-7, 27, g++-7, gcc-7 g++-7, ubuntu:20.04, 1.17, 3.24.0)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-14, -O3, 25, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-18, -O3, 25, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (gcc-11, -O3, 25, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-18, -O3, 27, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-11, 27, clang++-11, clang-11, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu:20.04, 1...
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (gcc-9, -O3, 27, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-14, -O3, 27, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-18, -O3, 26, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-15, 27, clang++-15, clang-15, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-24.04, 1...
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (cc, 22, ubuntu:20.04, c++, 1.8, 3.18.0, g++)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (gcc-10, 27, g++-10, gcc-10 g++-10, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-22.04, 1....
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (gcc-12, 27, g++-12, gcc-12 g++-12, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-24.04, 1....
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (cc, 27, ubuntu:20.04, c++, 1.17, 3.24.0, g++)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (gcc-8, 27, g++-8, gcc-8 g++-8, ubuntu:20.04, 1.17, 3.24.0)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (arm-linux-gnueabihf-gcc, -mcpu=cortex-a7 -mfloat-abi=hard -O2 -mthumb -mthumb-int...
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-17, 27, clang++-17, clang-17, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-24.04, 1...
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (gcc-14, -Os, 27, ubuntu-24.04, g++-14, 1.17, 3.24.0, gcc-14 g++-14)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-16, 27, clang++-16, clang-16, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-24.04, 1...
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (cc, 24, ubuntu:20.04, c++, 1.14, 3.23.0, g++)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-12, 27, clang++-12, clang-12, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-22.04, 1...
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (cc, 23, ubuntu:20.04, c++, 1.11, 3.20.0, g++)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (cc, master, ubuntu-24.04, c++, main, 3.24.0)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (s390x-linux-gnu-gcc, -O2, 28, ubuntu-24.04, s390x-linux-gnu-g++, 1.17, 3.24.0, -D...
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (cc, 21, ubuntu:20.04, c++, 1.8, 3.15.2, g++)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (cc, 27, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_USE_32BIT_FLOAT=ON)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF, x86_64)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (gcc-10, -m32 -O3, 23, ubuntu:20.04, g++-10, 1.11, 3.20.0, -DAVM_CREATE_STACKTRACE...
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-18, -Os, 27, ubuntu-24.04, clang++-18, 1.17, 3.24.0, clang-18)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, -O2, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g...
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (arm-linux-gnueabihf-gcc, -mcpu=cortex-a7 -mfloat-abi=hard -O2 -mthumb -mthumb-int...
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, -O2, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g...
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-10, -O3, 27, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-10, -O3, 27, 1.11.1)
The operation was canceled.
|
|
build-and-test (gcc-13, -O3, 26, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (gcc-13, -O3, 26, 1.11.1)
The operation was canceled.
|
|
build-and-test (clang-13, 27, clang++-13, clang-13, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-22.04, 1...
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-13, 27, clang++-13, clang-13, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-22.04, 1...
The operation was canceled.
|
|
build-and-test (cc, 27, ubuntu-22.04, c++, 1.17, 3.24.0)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (cc, 27, ubuntu-22.04, c++, 1.17, 3.24.0)
The operation was canceled.
|
|
build-and-test (clang-14, -O3, 26, 1.11.1)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (clang-14, -O3, 26, 1.11.1)
The operation was canceled.
|
|
build-and-test (gcc-14, 27, g++-14, gcc-14 g++-14, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-24.04, 1....
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (gcc-14, 27, g++-14, gcc-14 g++-14, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-24.04, 1....
The operation was canceled.
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF, aarch64)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF, aarch64)
The operation was canceled.
|
|
Build and Test
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (cc, -O2, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_WARNINGS_ARE_ERRORS=OFF)
Canceling since a higher priority waiting request for Build and Test-refs/pull/1165/merge exists
|
|
build-and-test (cc, -O2, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_WARNINGS_ARE_ERRORS=OFF)
The operation was canceled.
|
|
build-and-test (gcc-9, -O3, 26, 1.11.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-9, -O3, 26, 1.11.1)
Unused private function
|
|
build-and-test (gcc-9, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-9, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-9, -O3, 26, 1.11.1)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-9, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-9, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-9, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-9, -O3, 26, 1.11.1)
You are using deprecated ImageOS ubuntu-20.04. Support for maintenance is very limited. Consider a non-deprecated version as mentioned in the README.md.
|
|
build-and-test (gcc-11, -O3, 26, 1.11.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-11, -O3, 26, 1.11.1)
Unused private function
|
|
build-and-test (gcc-11, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-11, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-11, -O3, 26, 1.11.1)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-11, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-11, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-11, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-10, -O3, 27, 1.11.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-10, -O3, 27, 1.11.1)
Unused private function
|
|
build-and-test (clang-10, -O3, 27, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-10, -O3, 27, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-10, -O3, 27, 1.11.1)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-10, -O3, 27, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-10, -O3, 27, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-10, -O3, 27, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-10, -O3, 27, 1.11.1)
You are using deprecated ImageOS ubuntu-20.04. Support for maintenance is very limited. Consider a non-deprecated version as mentioned in the README.md.
|
|
build-and-test (gcc-13, -O3, 26, 1.11.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-13, -O3, 26, 1.11.1)
Unused private function
|
|
build-and-test (gcc-13, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-13, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-13, -O3, 26, 1.11.1)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-13, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-13, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-13, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-13, 27, clang++-13, clang-13, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-22.04, 1...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-13, 27, clang++-13, clang-13, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-22.04, 1...
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-13, 27, clang++-13, clang-13, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-22.04, 1...
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-13, 27, clang++-13, clang-13, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-22.04, 1...
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-13, 27, clang++-13, clang-13, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-22.04, 1...
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-13, 27, clang++-13, clang-13, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-22.04, 1...
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-13, 27, clang++-13, clang-13, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-22.04, 1...
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, 27, ubuntu-22.04, c++, 1.17, 3.24.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, 27, ubuntu-22.04, c++, 1.17, 3.24.0)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, 27, ubuntu-22.04, c++, 1.17, 3.24.0)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, 27, ubuntu-22.04, c++, 1.17, 3.24.0)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (cc, 27, ubuntu-22.04, c++, 1.17, 3.24.0)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, 27, ubuntu-22.04, c++, 1.17, 3.24.0)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, 27, ubuntu-22.04, c++, 1.17, 3.24.0)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-14, -O3, 26, 1.11.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-14, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-14, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-14, -O3, 26, 1.11.1)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-14, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-14, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (clang-14, -O3, 26, 1.11.1)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-14, 27, g++-14, gcc-14 g++-14, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-24.04, 1....
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-14, 27, g++-14, gcc-14 g++-14, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-24.04, 1....
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-14, 27, g++-14, gcc-14 g++-14, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-24.04, 1....
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-14, 27, g++-14, gcc-14 g++-14, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-24.04, 1....
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-14, 27, g++-14, gcc-14 g++-14, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-24.04, 1....
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-14, 27, g++-14, gcc-14 g++-14, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-24.04, 1....
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (gcc-14, 27, g++-14, gcc-14 g++-14, -DAVM_WARNINGS_ARE_ERRORS=ON, ubuntu-24.04, 1....
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF, aarch64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF, aarch64)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF, aarch64)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF, aarch64)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF, aarch64)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF, aarch64)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF, aarch64)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, -O2, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_WARNINGS_ARE_ERRORS=OFF)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, -O2, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_WARNINGS_ARE_ERRORS=OFF)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, -O2, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_WARNINGS_ARE_ERRORS=OFF)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, -O2, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_WARNINGS_ARE_ERRORS=OFF)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (cc, -O2, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_WARNINGS_ARE_ERRORS=OFF)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, -O2, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_WARNINGS_ARE_ERRORS=OFF)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|
|
build-and-test (cc, -O2, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_WARNINGS_ARE_ERRORS=OFF)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
|