Merge pull request #2268 from pguyot/w16/renode-1.16.1 #7174
Annotations
167 errors and 548 warnings
|
build-and-test (clang-10, clang++-10, clang-10, ubuntu:20.04)
Process completed with exit code 2.
|
|
build-and-test (gcc-12, g++-12, gcc-12 g++-12)
Process completed with exit code 1.
|
|
build-and-test (clang-12, clang++-12, clang-12, ubuntu-22.04)
Process completed with exit code 1.
|
|
build-and-test (gcc-8, g++-8, gcc-8 g++-8, ubuntu:20.04)
Process completed with exit code 1.
|
|
build-and-test (cc, ubuntu-24.04-arm, c++)
Process completed with exit code 1.
|
|
build-and-test (cc, master, c++, main)
Could not mix rebar from any hex.pm mirror
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
Process completed with exit code 139.
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...:
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -DAVM_DISABLE_JIT=OFF, aarch64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -DAVM_DISABLE_JIT=OFF, aarch64):
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -DAVM_DISABLE_JIT=OFF, aarch64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -DAVM_DISABLE_JIT=OFF, aarch64):
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -DAVM_DISABLE_JIT=OFF, aarch64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -DAVM_DISABLE_JIT=OFF, aarch64):
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -DAVM_DISABLE_JIT=OFF, aarch64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -DAVM_DISABLE_JIT=OFF, aarch64):
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -DAVM_DISABLE_JIT=OFF, aarch64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -DAVM_DISABLE_JIT=OFF, aarch64):
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro 'PROCESS_SIGNAL_MESSAGES'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...:
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro 'SET_ERROR'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro 'PROCESS_SIGNAL_MESSAGES'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro 'SET_ERROR'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro 'PROCESS_SIGNAL_MESSAGES'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro 'SET_ERROR'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro 'PROCESS_SIGNAL_MESSAGES'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro 'SET_ERROR'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro 'PROCESS_SIGNAL_MESSAGES'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro 'SET_ERROR'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro 'PROCESS_SIGNAL_MESSAGES'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro 'SET_ERROR'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro 'PROCESS_SIGNAL_MESSAGES'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro 'SET_ERROR'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro 'PROCESS_SIGNAL_MESSAGES'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro 'SET_ERROR'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro 'PROCESS_SIGNAL_MESSAGES'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro 'SET_ERROR'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro 'PROCESS_SIGNAL_MESSAGES'
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro 'SET_ERROR'
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...:
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...:
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...:
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...:
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...:
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L827
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L819
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L1723
note: in expansion of macro ‘PROCESS_SIGNAL_MESSAGES’
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L804
note: in expansion of macro ‘SET_ERROR’
|
|
build-and-test (clang-10, clang++-10, clang-10, ubuntu:20.04)
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, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-10, clang++-10, clang-10, ubuntu:20.04)
No files were found with the provided path: core/*. No artifacts will be uploaded.
|
|
build-and-test (clang-10, clang++-10, clang-10, ubuntu:20.04):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (clang-10, clang++-10, clang-10, ubuntu:20.04)
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, clang++-10, clang-10, ubuntu:20.04)
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, clang++-10, clang-10, ubuntu:20.04)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-10, clang++-10, clang-10, ubuntu:20.04)
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, clang++-10, clang-10, ubuntu:20.04)
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, clang++-10, clang-10, ubuntu:20.04)
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, clang++-10, clang-10, ubuntu:20.04)
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 (clang-18, 28)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-18, 28):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (clang-18, 28)
Unused private function
|
|
build-and-test (clang-18, 28)
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-18, 28)
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-18, 28)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-18, 28)
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-18, 28)
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-18, 28)
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, 27)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-11, 27):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (gcc-11, 27)
Unused private function
|
|
build-and-test (gcc-11, 27)
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, 27)
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, 27)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-11, 27)
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, 27)
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, 27)
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-12, g++-12, gcc-12 g++-12)
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, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-12, g++-12, gcc-12 g++-12)
No files were found with the provided path: core/*. No artifacts will be uploaded.
|
|
build-and-test (gcc-12, g++-12, gcc-12 g++-12):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (gcc-12, g++-12, gcc-12 g++-12)
Unused private function
|
|
build-and-test (gcc-12, g++-12, gcc-12 g++-12)
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-12, g++-12, gcc-12 g++-12)
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-12, g++-12, gcc-12 g++-12)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-12, g++-12, gcc-12 g++-12)
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-12, g++-12, gcc-12 g++-12)
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-12, g++-12, gcc-12 g++-12)
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-12, clang++-12, clang-12, ubuntu-22.04)
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, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-12, clang++-12, clang-12, ubuntu-22.04)
No files were found with the provided path: core/*. No artifacts will be uploaded.
|
|
build-and-test (clang-12, clang++-12, clang-12, ubuntu-22.04):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (clang-12, clang++-12, clang-12, ubuntu-22.04)
Unused private function
|
|
build-and-test (clang-12, clang++-12, clang-12, ubuntu-22.04)
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-12, clang++-12, clang-12, ubuntu-22.04)
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-12, clang++-12, clang-12, ubuntu-22.04)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-12, clang++-12, clang-12, ubuntu-22.04)
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-12, clang++-12, clang-12, ubuntu-22.04)
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-12, clang++-12, clang-12, ubuntu-22.04)
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, 26)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-14, 26):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (clang-14, 26)
Unused private function
|
|
build-and-test (clang-14, 26)
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, 26)
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, 26)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-14, 26)
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, 26)
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, 26)
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, clang++-13, clang-13, ubuntu-22.04)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-13, clang++-13, clang-13, ubuntu-22.04):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (clang-13, clang++-13, clang-13, ubuntu-22.04)
Unused private function
|
|
build-and-test (clang-13, clang++-13, clang-13, ubuntu-22.04)
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, clang++-13, clang-13, ubuntu-22.04)
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, clang++-13, clang-13, ubuntu-22.04)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-13, clang++-13, clang-13, ubuntu-22.04)
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, clang++-13, clang-13, ubuntu-22.04)
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, clang++-13, clang-13, ubuntu-22.04)
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, 26)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-11, 26):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (gcc-11, 26)
Unused private function
|
|
build-and-test (gcc-11, 26)
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, 26)
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, 26)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-11, 26)
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, 26)
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, 26)
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-8, g++-8, gcc-8 g++-8, ubuntu:20.04)
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, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-8, g++-8, gcc-8 g++-8, ubuntu:20.04)
No files were found with the provided path: core/*. No artifacts will be uploaded.
|
|
build-and-test (gcc-8, g++-8, gcc-8 g++-8, ubuntu:20.04):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (gcc-8, g++-8, gcc-8 g++-8, ubuntu:20.04)
Unused private function
|
|
build-and-test (gcc-8, g++-8, gcc-8 g++-8, ubuntu:20.04)
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-8, g++-8, gcc-8 g++-8, ubuntu:20.04)
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-8, g++-8, gcc-8 g++-8, ubuntu:20.04)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-8, g++-8, gcc-8 g++-8, ubuntu:20.04)
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-8, g++-8, gcc-8 g++-8, ubuntu:20.04)
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-8, g++-8, gcc-8 g++-8, ubuntu:20.04)
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-8, g++-8, gcc-8 g++-8, ubuntu:20.04)
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-14, g++-14, gcc-14 g++-14)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-14, g++-14, gcc-14 g++-14):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (gcc-14, g++-14, gcc-14 g++-14)
Unused private function
|
|
build-and-test (gcc-14, g++-14, gcc-14 g++-14)
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, g++-14, gcc-14 g++-14)
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, g++-14, gcc-14 g++-14)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-14, g++-14, gcc-14 g++-14)
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, g++-14, gcc-14 g++-14)
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, g++-14, gcc-14 g++-14)
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, ubuntu-24.04-arm, c++)
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, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, ubuntu-24.04-arm, c++)
No files were found with the provided path: core/*. No artifacts will be uploaded.
|
|
build-and-test (cc, ubuntu-24.04-arm, c++):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (cc, ubuntu-24.04-arm, c++)
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, ubuntu-24.04-arm, c++)
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, ubuntu-24.04-arm, c++)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (cc, ubuntu-24.04-arm, c++)
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, ubuntu-24.04-arm, c++)
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, ubuntu-24.04-arm, c++)
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, 28)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-13, 28):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (gcc-13, 28)
Unused private function
|
|
build-and-test (gcc-13, 28)
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, 28)
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, 28)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-13, 28)
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, 28)
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, 28)
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, 26)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-13, 26):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (gcc-13, 26)
Unused private function
|
|
build-and-test (gcc-13, 26)
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, 26)
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, 26)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-13, 26)
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, 26)
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, 26)
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-15, clang++-15, clang-15)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-15, clang++-15, clang-15):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (clang-15, clang++-15, clang-15)
Unused private function
|
|
build-and-test (clang-15, clang++-15, clang-15)
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-15, clang++-15, clang-15)
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-15, clang++-15, clang-15)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-15, clang++-15, clang-15)
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-15, clang++-15, clang-15)
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-15, clang++-15, clang-15)
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, c++, 1.17)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, 27, c++, 1.17):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (cc, 27, c++, 1.17)
Unused private function
|
|
build-and-test (cc, 27, c++, 1.17)
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, c++, 1.17)
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, c++, 1.17)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (cc, 27, c++, 1.17)
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, c++, 1.17)
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, c++, 1.17)
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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-18, 26)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-18, 26):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (clang-18, 26)
Unused private function
|
|
build-and-test (clang-18, 26)
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-18, 26)
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-18, 26)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-18, 26)
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-18, 26)
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-18, 26)
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, c++, 1.18)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, 27, c++, 1.18):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (cc, 27, c++, 1.18)
Unused private function
|
|
build-and-test (cc, 27, c++, 1.18)
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, c++, 1.18)
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, c++, 1.18)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (cc, 27, c++, 1.18)
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, c++, 1.18)
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, c++, 1.18)
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-10, g++-10, gcc-10 g++-10)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-10, g++-10, gcc-10 g++-10):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (gcc-10, g++-10, gcc-10 g++-10)
Unused private function
|
|
build-and-test (gcc-10, g++-10, gcc-10 g++-10)
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-10, g++-10, gcc-10 g++-10)
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-10, g++-10, gcc-10 g++-10)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-10, g++-10, gcc-10 g++-10)
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-10, g++-10, gcc-10 g++-10)
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-10, g++-10, gcc-10 g++-10)
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-10, ubuntu:20.04, g++-10, -m32 -O3, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNIN...
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-10, ubuntu:20.04, g++-10, -m32 -O3, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNIN...:
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
|
|
build-and-test (gcc-10, ubuntu:20.04, g++-10, -m32 -O3, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNIN...
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-10, ubuntu:20.04, g++-10, -m32 -O3, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNIN...
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-10, ubuntu:20.04, g++-10, -m32 -O3, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNIN...
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-10, ubuntu:20.04, g++-10, -m32 -O3, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNIN...
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-10, ubuntu:20.04, g++-10, -m32 -O3, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNIN...
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-10, ubuntu:20.04, g++-10, -m32 -O3, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNIN...
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-10, ubuntu:20.04, g++-10, -m32 -O3, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNIN...
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-9, g++-9, gcc-9 g++-9)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-9, g++-9, gcc-9 g++-9):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (gcc-9, g++-9, gcc-9 g++-9)
Unused private function
|
|
build-and-test (gcc-9, g++-9, gcc-9 g++-9)
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, g++-9, gcc-9 g++-9)
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, g++-9, gcc-9 g++-9)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-9, g++-9, gcc-9 g++-9)
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, g++-9, gcc-9 g++-9)
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, g++-9, gcc-9 g++-9)
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-16, clang++-16, clang-16)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-16, clang++-16, clang-16):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (clang-16, clang++-16, clang-16)
Unused private function
|
|
build-and-test (clang-16, clang++-16, clang-16)
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-16, clang++-16, clang-16)
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-16, clang++-16, clang-16)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-16, clang++-16, clang-16)
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-16, clang++-16, clang-16)
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-16, clang++-16, clang-16)
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, 26, c++, 1.17)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, 26, c++, 1.17):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (cc, 26, c++, 1.17)
Unused private function
|
|
build-and-test (cc, 26, c++, 1.17)
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, 26, c++, 1.17)
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, 26, c++, 1.17)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (cc, 26, c++, 1.17)
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, 26, c++, 1.17)
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, 26, c++, 1.17)
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-18, 27)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-18, 27):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (clang-18, 27)
Unused private function
|
|
build-and-test (clang-18, 27)
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-18, 27)
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-18, 27)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-18, 27)
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-18, 27)
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-18, 27)
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, master, c++, main)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, master, c++, main)
No files were found with the provided path: core/*. No artifacts will be uploaded.
|
|
build-and-test (clang-14, 27)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-14, 27):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (clang-14, 27)
Unused private function
|
|
build-and-test (clang-14, 27)
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, 27)
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, 27)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-14, 27)
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, 27)
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, 27)
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-7, g++-7, gcc-7 g++-7, ubuntu:20.04, )
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-7, g++-7, gcc-7 g++-7, ubuntu:20.04, ):
src/libAtomVM/otp_socket.c#L584
ISO C99 requires at least one argument for the "..." in a variadic macro
|
|
build-and-test (gcc-7, g++-7, gcc-7 g++-7, ubuntu:20.04, ):
src/libAtomVM/otp_socket.c#L496
ISO C99 requires at least one argument for the "..." in a variadic macro
|
|
build-and-test (gcc-7, g++-7, gcc-7 g++-7, ubuntu:20.04, ):
src/libAtomVM/otp_socket.c#L473
ISO C99 requires at least one argument for the "..." in a variadic macro
|
|
build-and-test (gcc-7, g++-7, gcc-7 g++-7, ubuntu:20.04, ):
src/libAtomVM/otp_socket.c#L453
ISO C99 requires at least one argument for the "..." in a variadic macro
|
|
build-and-test (gcc-7, g++-7, gcc-7 g++-7, ubuntu:20.04, )
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-7, g++-7, gcc-7 g++-7, ubuntu:20.04, )
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-7, g++-7, gcc-7 g++-7, ubuntu:20.04, )
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-7, g++-7, gcc-7 g++-7, ubuntu:20.04, )
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-7, g++-7, gcc-7 g++-7, ubuntu:20.04, )
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-7, g++-7, gcc-7 g++-7, ubuntu:20.04, )
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-7, g++-7, gcc-7 g++-7, ubuntu:20.04, )
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 (clang-14, 28)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-14, 28):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (clang-14, 28)
Unused private function
|
|
build-and-test (clang-14, 28)
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, 28)
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, 28)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-14, 28)
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, 28)
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, 28)
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 (s390x-linux-gnu-gcc, s390x-linux-gnu-g++, -DAVM_WARNINGS_ARE_ERRORS=ON -DCMAKE_TO...
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (s390x-linux-gnu-gcc, s390x-linux-gnu-g++, -DAVM_WARNINGS_ARE_ERRORS=ON -DCMAKE_TO...:
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
|
|
build-and-test (s390x-linux-gnu-gcc, s390x-linux-gnu-g++, -DAVM_WARNINGS_ARE_ERRORS=ON -DCMAKE_TO...
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 (s390x-linux-gnu-gcc, s390x-linux-gnu-g++, -DAVM_WARNINGS_ARE_ERRORS=ON -DCMAKE_TO...
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 (s390x-linux-gnu-gcc, s390x-linux-gnu-g++, -DAVM_WARNINGS_ARE_ERRORS=ON -DCMAKE_TO...
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (s390x-linux-gnu-gcc, s390x-linux-gnu-g++, -DAVM_WARNINGS_ARE_ERRORS=ON -DCMAKE_TO...
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 (s390x-linux-gnu-gcc, s390x-linux-gnu-g++, -DAVM_WARNINGS_ARE_ERRORS=ON -DCMAKE_TO...
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 (s390x-linux-gnu-gcc, s390x-linux-gnu-g++, -DAVM_WARNINGS_ARE_ERRORS=ON -DCMAKE_TO...
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, g++-14, -Os, gcc-14 g++-14)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-14, g++-14, -Os, gcc-14 g++-14):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (gcc-14, g++-14, -Os, gcc-14 g++-14)
Unused private function
|
|
build-and-test (gcc-14, g++-14, -Os, gcc-14 g++-14)
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, g++-14, -Os, gcc-14 g++-14)
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, g++-14, -Os, gcc-14 g++-14)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-14, g++-14, -Os, gcc-14 g++-14)
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, g++-14, -Os, gcc-14 g++-14)
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, g++-14, -Os, gcc-14 g++-14)
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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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, c++, de_DE.UTF-8)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, c++, de_DE.UTF-8):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (cc, c++, de_DE.UTF-8)
Unused private function
|
|
build-and-test (cc, c++, de_DE.UTF-8)
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, c++, de_DE.UTF-8)
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, c++, de_DE.UTF-8)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (cc, c++, de_DE.UTF-8)
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, c++, de_DE.UTF-8)
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, c++, de_DE.UTF-8)
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 (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...
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 (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...
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 (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...
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 (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...
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 (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...
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, 28)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-11, 28):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (gcc-11, 28)
Unused private function
|
|
build-and-test (gcc-11, 28)
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, 28)
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, 28)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-11, 28)
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, 28)
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, 28)
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, c++, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNINGS_ARE_ERRORS=ON)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, c++, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNINGS_ARE_ERRORS=ON):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (cc, c++, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNINGS_ARE_ERRORS=ON)
Unused private function
|
|
build-and-test (cc, c++, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNINGS_ARE_ERRORS=ON)
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, c++, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNINGS_ARE_ERRORS=ON)
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, c++, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNINGS_ARE_ERRORS=ON)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (cc, c++, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNINGS_ARE_ERRORS=ON)
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, c++, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNINGS_ARE_ERRORS=ON)
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, c++, -DAVM_CREATE_STACKTRACES=off -DAVM_WARNINGS_ARE_ERRORS=ON)
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, 27)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (gcc-13, 27):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (gcc-13, 27)
Unused private function
|
|
build-and-test (gcc-13, 27)
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, 27)
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, 27)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (gcc-13, 27)
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, 27)
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, 27)
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-11, clang++-11, clang-11, ubuntu:20.04)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-11, clang++-11, clang-11, ubuntu:20.04):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (clang-11, clang++-11, clang-11, ubuntu:20.04)
Unused private function
|
|
build-and-test (clang-11, clang++-11, clang-11, ubuntu:20.04)
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-11, clang++-11, clang-11, ubuntu:20.04)
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-11, clang++-11, clang-11, ubuntu:20.04)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-11, clang++-11, clang-11, ubuntu:20.04)
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-11, clang++-11, clang-11, ubuntu:20.04)
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-11, clang++-11, clang-11, ubuntu:20.04)
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-11, clang++-11, clang-11, ubuntu:20.04)
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-g++, -mcpu=cortex-a7 -mfloat-abi=har...
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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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, 26, c++, 1.18)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, 26, c++, 1.18):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (cc, 26, c++, 1.18)
Unused private function
|
|
build-and-test (cc, 26, c++, 1.18)
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, 26, c++, 1.18)
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, 26, c++, 1.18)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (cc, 26, c++, 1.18)
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, 26, c++, 1.18)
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, 26, c++, 1.18)
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, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
Unused private function
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
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, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
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, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
_.._ 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, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
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, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
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, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
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, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (cc, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
Unused private function
|
|
build-and-test (cc, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
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, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
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, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (cc, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
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, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
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, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
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-17, clang++-17, clang-17)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (clang-17, clang++-17, clang-17):
tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
|
|
build-and-test (clang-17, clang++-17, clang-17)
Unused private function
|
|
build-and-test (clang-17, clang++-17, clang-17)
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-17, clang++-17, clang-17)
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-17, clang++-17, clang-17)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (clang-17, clang++-17, clang-17)
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-17, clang++-17, clang-17)
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-17, clang++-17, clang-17)
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 -DAVM_DISABLE_...
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 28, ubuntu-24.04-arm, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_...
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 -DAVM_DISABLE_...
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 -DAVM_DISABLE_...
_.._ 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 -DAVM_DISABLE_...
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 -DAVM_DISABLE_...
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 -DAVM_DISABLE_...
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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 1.17, 3.24.0...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (riscv64-linux-gnu-gcc, 28, ubuntu-24.04, riscv64-linux-gnu-g++, -O2, 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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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 (arm-linux-gnueabihf-gcc, 28, ubuntu-24.04, arm-linux-gnueabihf-g++, -mcpu=cortex-...
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, ubuntu-24.04-arm, c++, -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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -DAVM_DISABLE_JIT=OFF, aarch64):
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -DAVM_DISABLE_JIT=OFF, aarch64):
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -DAVM_DISABLE_JIT=OFF, aarch64):
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -DAVM_DISABLE_JIT=OFF, aarch64):
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, ubuntu-24.04-arm, c++, -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, ubuntu-24.04-arm, c++, -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, ubuntu-24.04-arm, c++, -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, ubuntu-24.04-arm, c++, -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, ubuntu-24.04-arm, c++, -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, ubuntu-24.04-arm, c++, -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 (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...
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 (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...
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 (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...
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 (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...
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 (riscv32-unknown-linux-gnu-gcc, 28, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -...
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 (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...
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 (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...
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 (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...
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 (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...
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 (riscv32-unknown-linux-gnu-gcc, ubuntu-24.04, riscv32-unknown-linux-gnu-g++, -DAVM...
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, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...
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, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...
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, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (cc, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...
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, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...
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, 29.0-rc1, ubuntu-24.04, c++, strict, 1.19.5, 3.27.0, -DAVM_DISABLE_JIT=OFF, x...
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, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...:
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...
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, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...
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, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...
_.._ 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, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...
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, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...
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, c++, 1.17, 3.24.0, -DAVM_DISABLE_JIT=OFF -DAVM_DISABLE_JIT_...
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, c++, -DAVM_DISABLE_JIT=OFF, x86_64)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, 28, ubuntu-24.04, c++, -DAVM_DISABLE_JIT=OFF, x86_64)
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, c++, -DAVM_DISABLE_JIT=OFF, x86_64)
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, c++, -DAVM_DISABLE_JIT=OFF, x86_64)
_.._ 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, c++, -DAVM_DISABLE_JIT=OFF, x86_64)
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, c++, -DAVM_DISABLE_JIT=OFF, x86_64)
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, c++, -DAVM_DISABLE_JIT=OFF, x86_64)
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, c++, -DAVM_DISABLE_JIT=OFF, x86_64)
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64):
src/libAtomVM/opcodesswitch.h#L104
ISO C forbids conversion of function pointer to object pointer type [-Wpedantic]
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64)
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, c++, -DAVM_DISABLE_JIT=OFF, x86_64)
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, c++, -DAVM_DISABLE_JIT=OFF, x86_64)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
|
|
build-and-test (cc, c++, -DAVM_DISABLE_JIT=OFF, x86_64)
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, c++, -DAVM_DISABLE_JIT=OFF, x86_64)
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, c++, -DAVM_DISABLE_JIT=OFF, x86_64)
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
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
core--arm-linux-gnueabihf-gcc-28-24443471787-1
Expired
|
21.6 MB |
sha256:b3237542c0d963f5cf940aa42defe259e52a1cedf59f39ea3e40b59853650416
|
|