Skip to content

Fix symbol visibility issues, add test for it #572

Fix symbol visibility issues, add test for it

Fix symbol visibility issues, add test for it #572

Triggered via pull request October 16, 2024 11:34
Status Failure
Total duration 45m 14s
Artifacts

ci.yml

on: pull_request
Build Docker image
20m 34s
Build Docker image
x64 (MSVC): C++ (public headers)
19s
x64 (MSVC): C++ (public headers)
SageMath prover
57s
SageMath prover
release
3m 2s
release
Matrix: ARM64: macOS Sonoma
Matrix: win64-native
Matrix: x86_64: macOS Monterey, Valgrind
s390x (big-endian): Linux (Debian stable, QEMU)
2m 45s
s390x (big-endian): Linux (Debian stable, QEMU)
ppc64le: Linux (Debian stable, QEMU)
3m 18s
ppc64le: Linux (Debian stable, QEMU)
C++ -fpermissive (entire project)
2m 3s
C++ -fpermissive (entire project)
C++ (public headers)
1m 39s
C++ (public headers)
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)
Fit to window
Zoom out
Zoom in

Annotations

49 errors and 10 warnings
x64 (MSVC): Windows (VS 2022, int128_struct with __(u)mulh)
Process completed with exit code 1.
x86 (MSVC): Windows (VS 2022)
Process completed with exit code 1.
x64 (MSVC): Windows (VS 2022, int128_struct)
Process completed with exit code 1.
x64 (MSVC): Windows (VS 2022, shared)
Process completed with exit code 1.
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, yes)
Process completed with exit code 1.
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, yes, gcc)
Process completed with exit code 1.
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes)
Process completed with exit code 1.
x86_64: macOS Monterey, Valgrind (int64, yes, yes, yes, yes, yes, yes)
Process completed with exit code 1.
ARM64: Linux (Debian stable, QEMU)
Process completed with exit code 1.
ARM32: Linux (Debian stable, QEMU)
Process completed with exit code 1.
C++ -fpermissive (entire project)
Process completed with exit code 1.
ARM32: Linux (Debian stable, QEMU) (yes, arm32)
Process completed with exit code 1.
Valgrind (memcheck) (clang, auto)
Process completed with exit code 1.
Valgrind (memcheck) (clang, no, 2, 2)
Process completed with exit code 1.
ARM64: Linux (Debian stable, QEMU) (clang --target=aarch64-linux-gnu)
Process completed with exit code 1.
ARM64: Linux (Debian stable, QEMU) (clang-snapshot --target=aarch64-linux-gnu)
Process completed with exit code 1.
s390x (big-endian): Linux (Debian stable, QEMU)
Process completed with exit code 1.
i686: Linux (Debian stable) (i686-linux-gnu-gcc)
Process completed with exit code 1.
ppc64le: Linux (Debian stable, QEMU)
Process completed with exit code 1.
Valgrind (memcheck) (i686-linux-gnu-gcc, i686-linux-gnu, no, 2, 2)
Process completed with exit code 1.
Valgrind (memcheck) (i686-linux-gnu-gcc, i686-linux-gnu, auto)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (-O1, yes, yes, yes, yes, yes, yes, gcc-snapshot)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (-O1, yes, yes, yes, yes, yes, yes, clang-snapshot)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (-O1, yes, yes, yes, yes, yes, yes, gcc)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (-O1, yes, yes, yes, yes, yes, yes, clang)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (int128, yes, yes, yes, yes, yes, gcc-snapshot)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (int128, yes, yes, yes, yes, clang)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (int128, yes, yes, yes, yes, yes, clang)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (int128, yes, yes, yes, yes, yes, gcc)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (int128, yes, yes, yes, yes, clang-snapshot)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (int128, yes, yes, yes, yes, gcc-snapshot)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (int128, yes, yes, yes, yes, yes, clang-snapshot)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (int128, yes, yes, yes, yes, gcc)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (no, yes, yes, yes, yes, yes, -DVERIFY, clang)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (no, yes, yes, yes, yes, yes, -DVERIFY, gcc)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (yes, yes, yes, yes, clang-snapshot)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (int64, yes, yes, yes, yes, yes, clang)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (yes, yes, yes, yes, gcc-snapshot)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (int64, yes, yes, yes, yes, yes, gcc)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (int64, yes, yes, yes, yes, yes, gcc-snapshot)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (int64, yes, yes, yes, yes, yes, clang-snapshot)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (yes, yes, yes, yes, gcc)
Process completed with exit code 1.
x86_64: Linux (Debian stable) (yes, yes, yes, yes, clang)
Process completed with exit code 1.
x86_64: macOS Monterey, Valgrind (int128_struct, 2, 4)
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
x86_64: macOS Monterey, Valgrind (distcheck)
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
x86_64: macOS Monterey, Valgrind (int128, yes)
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, yes)
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, yes, gcc)
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, yes, -DVERIFY, no)
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes)
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
x86_64: macOS Monterey, Valgrind (int64, yes, yes, yes, yes, yes, yes)
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, yes, gcc, valgrind --error-exi...
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
x86_64: macOS Monterey, Valgrind (int128, yes, yes, yes, yes, yes, yes, valgrind --error-exitcode...
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721