Add BIP352 silentpayments module
#453
josibakeci.yml
on: pull_request
Build Docker image
18m 49s
x64 (MSVC): C++ (public headers)
31s
SageMath prover
57s
release
2m 56s
Matrix: ARM64: macOS Sonoma
Matrix: win64-native
Matrix: x86_64: macOS Monterey, Valgrind
s390x (big-endian): Linux (Debian stable, QEMU)
9m 29s
ppc64le: Linux (Debian stable, QEMU)
6m 11s
C++ -fpermissive (entire project)
3m 58s
C++ (public headers)
2m 40s
Matrix: ARM32: Linux (Debian stable, QEMU)
Matrix: ARM64: Linux (Debian stable, QEMU)
Matrix: i686: Linux (Debian stable)
Matrix: x86_64: Linux (Debian stable)
Matrix: mingw_debian
Matrix: MSan
Matrix: UBSan, ASan, LSan
Matrix: Valgrind (memcheck)
Annotations
45 errors and 28 warnings
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes)
Process completed with exit code 134.
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, gcc)
Process completed with exit code 134.
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes)
Process completed with exit code 134.
|
|
x86_64: macOS Monterey, Valgrind (int64, yes, yes, yes, yes, yes)
Process completed with exit code 134.
|
|
C++ -fpermissive (entire project)
Process completed with exit code 134.
|
|
x86_64 (mingw32-w64): Windows (Debian stable, Wine)
Process completed with exit code 3.
|
|
ppc64le: Linux (Debian stable, QEMU)
Process completed with exit code 134.
|
|
ARM64: Linux (Debian stable, QEMU) (clang --target=aarch64-linux-gnu)
Process completed with exit code 134.
|
|
ARM64: Linux (Debian stable, QEMU)
Process completed with exit code 134.
|
|
i686 (mingw32-w64): Windows (Debian stable, Wine)
Process completed with exit code 3.
|
|
i686: Linux (Debian stable) (i686-linux-gnu-gcc)
Process completed with exit code 134.
|
|
i686: Linux (Debian stable) (clang --target=i686-pc-linux-gnu -isystem /usr/i686-linux-gnu/include)
Process completed with exit code 134.
|
|
Valgrind (memcheck) (clang, no, 2, 2)
Process completed with exit code 134.
|
|
Valgrind (memcheck) (clang, auto)
Process completed with exit code 134.
|
|
MSan (-fsanitize=memory -fsanitize-recover=memory -fsanitize-memory-param-retval -g, no)
Process completed with exit code 134.
|
|
MSan (yes, -fsanitize=memory -fsanitize-recover=memory -g)
Process completed with exit code 134.
|
|
s390x (big-endian): Linux (Debian stable, QEMU)
Process completed with exit code 134.
|
|
MSan (2, 2, yes, -fsanitize=memory -fsanitize-recover=memory -g -O3)
Process completed with exit code 134.
|
|
ARM32: Linux (Debian stable, QEMU)
Process completed with exit code 134.
|
|
UBSan, ASan, LSan (clang, auto)
Process completed with exit code 134.
|
|
ARM32: Linux (Debian stable, QEMU) (yes, arm32)
Process completed with exit code 134.
|
|
ARM64: Linux (Debian stable, QEMU) (clang-snapshot --target=aarch64-linux-gnu)
Process completed with exit code 134.
|
|
UBSan, ASan, LSan (clang, no, 2, 2)
Process completed with exit code 134.
|
|
UBSan, ASan, LSan (i686-linux-gnu-gcc, i686-linux-gnu, no, 2, 2)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (-O1, yes, yes, yes, yes, yes, clang-snapshot)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (-O1, yes, yes, yes, yes, yes, clang)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (-O1, yes, yes, yes, yes, yes, gcc-snapshot)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (-O1, yes, yes, yes, yes, yes, gcc)
Process completed with exit code 134.
|
|
UBSan, ASan, LSan (i686-linux-gnu-gcc, i686-linux-gnu, auto)
Process completed with exit code 134.
|
|
Valgrind (memcheck) (i686-linux-gnu-gcc, i686-linux-gnu, no, 2, 2)
Process completed with exit code 134.
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, valgrind --error-exitcode=42, 2)
Process completed with exit code 134.
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, gcc, valgrind --error-exitcode...
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (int128, yes, yes, yes, clang-snapshot)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (int128, yes, yes, yes, gcc)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (int128, yes, yes, yes, gcc-snapshot)
Process completed with exit code 134.
|
|
Valgrind (memcheck) (i686-linux-gnu-gcc, i686-linux-gnu, auto)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (int128, yes, yes, yes, clang)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (int64, yes, yes, yes, yes, clang-snapshot)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (int64, yes, yes, yes, yes, clang)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (int64, yes, yes, yes, yes, gcc-snapshot)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (int64, yes, yes, yes, yes, gcc)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (no, yes, yes, yes, yes, -DVERIFY, gcc)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (no, yes, yes, yes, yes, -DVERIFY, clang-snapshot)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (no, yes, yes, yes, yes, -DVERIFY, gcc-snapshot)
Process completed with exit code 134.
|
|
x86_64: Linux (Debian stable) (no, yes, yes, yes, yes, -DVERIFY, clang)
Process completed with exit code 134.
|
|
ARM64: macOS Sonoma (int128, yes)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
ARM64: macOS Sonoma (int128_struct, 2, 4)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
ARM64: macOS Sonoma (int128, yes, yes, yes)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
ARM64: macOS Sonoma (int128, yes, yes, yes, yes)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
ARM64: macOS Sonoma (distcheck)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
ARM64: macOS Sonoma (int128, yes, yes, yes, yes, -DVERIFY)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
ARM64: macOS Sonoma (int128, yes, yes, yes, yes, gcc)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
ARM64: macOS Sonoma (int64, yes, yes, yes, yes)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
x86_64: macOS Monterey, Valgrind (int128_struct, 2, 4)
libtool 2.4.7 is already installed and up-to-date.
To reinstall 2.4.7, run:
brew reinstall libtool
|
|
x86_64: macOS Monterey, Valgrind (int128_struct, 2, 4)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
x86_64: macOS Monterey, Valgrind (distcheck)
libtool 2.4.7 is already installed and up-to-date.
To reinstall 2.4.7, run:
brew reinstall libtool
|
|
x86_64: macOS Monterey, Valgrind (distcheck)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes)
libtool 2.4.7 is already installed and up-to-date.
To reinstall 2.4.7, run:
brew reinstall libtool
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, gcc)
libtool 2.4.7 is already installed and up-to-date.
To reinstall 2.4.7, run:
brew reinstall libtool
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, gcc)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
x86_64: macOS Monterey, Valgrind (int128, yes)
libtool 2.4.7 is already installed and up-to-date.
To reinstall 2.4.7, run:
brew reinstall libtool
|
|
x86_64: macOS Monterey, Valgrind (int128, yes)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes)
libtool 2.4.7 is already installed and up-to-date.
To reinstall 2.4.7, run:
brew reinstall libtool
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, -DVERIFY, no)
libtool 2.4.7 is already installed and up-to-date.
To reinstall 2.4.7, run:
brew reinstall libtool
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, -DVERIFY, no)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
x86_64: macOS Monterey, Valgrind (int64, yes, yes, yes, yes, yes)
libtool 2.4.7 is already installed and up-to-date.
To reinstall 2.4.7, run:
brew reinstall libtool
|
|
x86_64: macOS Monterey, Valgrind (int64, yes, yes, yes, yes, yes)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, valgrind --error-exitcode=42, 2)
libtool 2.4.7 is already installed and up-to-date.
To reinstall 2.4.7, run:
brew reinstall libtool
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, valgrind --error-exitcode=42, 2)
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, gcc, valgrind --error-exitcode...
libtool 2.4.7 is already installed and up-to-date.
To reinstall 2.4.7, run:
brew reinstall libtool
|
|
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, gcc, valgrind --error-exitcode...
gcc 14.1.0_1 is already installed and up-to-date.
To reinstall 14.1.0_1, run:
brew reinstall gcc
|