WIP: Refactor representation of thread local state. #1912
Triggered via pull request
February 20, 2025 13:15
Status
Failure
Total duration
1h 4m 18s
Artifacts
–
main.yml
on: pull_request
Matrix: freebsd
Matrix: macos
Matrix: netbsd
Matrix: qemu-crossbuild
Matrix: sanitizer
Matrix: ubuntu
Matrix: windows
Format check
18s
Fuzzing
4m 42s
Matrix: gwp-asan
Matrix: self-vendored
all-checks
0s
Annotations
71 errors and 8 warnings
Format check
Process completed with exit code 1.
|
Self Vendored STL - macos-latest clang++
Process completed with exit code 1.
|
Mac OS macos-15 Debug -DSNMALLOC_USE_CXX17=ON
Process completed with exit code 1.
|
Mac OS macos-15 Debug
Process completed with exit code 1.
|
Mac OS macos-14 Release -DSNMALLOC_USE_CXX17=ON
Process completed with exit code 1.
|
Mac OS macos-14 Debug
Process completed with exit code 1.
|
Mac OS macos-14 Debug -DSNMALLOC_USE_CXX17=ON
Process completed with exit code 1.
|
Mac OS macos-15 Release -DSNMALLOC_USE_CXX17=ON
Process completed with exit code 1.
|
Mac OS macos-14 Release
Process completed with exit code 1.
|
Mac OS macos-13 Debug
Process completed with exit code 1.
|
Mac OS macos-13 Release
Process completed with exit code 1.
|
Mac OS macos-15 Release
Process completed with exit code 1.
|
Mac OS macos-13 Release -DSNMALLOC_USE_CXX17=ON
Process completed with exit code 1.
|
Mac OS macos-13 Debug -DSNMALLOC_USE_CXX17=ON
Process completed with exit code 1.
|
Windows - windows-2019 x64 Release Windows 8 compatible
Process completed with exit code 1.
|
Windows - windows-2022 x64 Release
Process completed with exit code 1.
|
Windows - windows-2022 x64 Debug -T ClangCL
Process completed with exit code 1.
|
Windows - windows-2019 x64 Debug
Process completed with exit code 1.
|
Windows - windows-2022 x64 Debug
Process completed with exit code 1.
|
Windows - windows-2022 Win32 Debug
Process completed with exit code 1.
|
Windows - windows-2022 ARM64EC Release
Process completed with exit code 1.
|
Windows - windows-2022 ARM64 Debug
Process completed with exit code 1.
|
Windows - windows-2019 Win32 Debug -T ClangCL
Process completed with exit code 1.
|
Windows - windows-2025 Win32 Debug -T ClangCL
Process completed with exit code 1.
|
Windows - windows-2022 ARM64 Release
Process completed with exit code 1.
|
Windows - windows-2019 x64 Release
Process completed with exit code 1.
|
Self Vendored STL - windows-2022 clang-cl
Process completed with exit code 1.
|
Windows - windows-2025 x64 Debug
Process completed with exit code 1.
|
Windows - windows-2019 x64 Debug -T ClangCL
Process completed with exit code 1.
|
Windows - windows-2022 Win32 Debug -T ClangCL
Process completed with exit code 1.
|
Windows - windows-2025 x64 Release
Process completed with exit code 1.
|
Windows - windows-2022 x64 Release -T ClangCL
Process completed with exit code 1.
|
Windows - windows-2025 Win32 Release
Process completed with exit code 1.
|
Windows - windows-2022 ARM64EC Debug
Process completed with exit code 1.
|
Windows - windows-2025 x64 Debug -T ClangCL
Process completed with exit code 1.
|
Windows - windows-2022 Win32 Release
Process completed with exit code 1.
|
Windows - windows-2025 Win32 Debug
Process completed with exit code 1.
|
Windows - windows-2019 x64 Release -T ClangCL
Process completed with exit code 1.
|
Windows - windows-2019 Win32 Debug
Process completed with exit code 1.
|
Windows - windows-2019 Win32 Release
Process completed with exit code 1.
|
Windows - windows-2022 Win32 Release -T ClangCL
Process completed with exit code 1.
|
Windows - windows-2019 Win32 Release -T ClangCL
Process completed with exit code 1.
|
Windows - windows-2025 Win32 Release -T ClangCL
Process completed with exit code 1.
|
Windows - windows-2025 x64 Release -T ClangCL
Process completed with exit code 1.
|
Ubuntu - ubuntu-24.04 Release
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
Ubuntu - ubuntu-24.04 Release
Process completed with exit code 143.
|
Ubuntu - ubuntu-22.04 Release
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
Ubuntu - ubuntu-22.04 Release
Process completed with exit code 143.
|
Self Vendored STL - ubuntu-24.04 clang++-18
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
Self Vendored STL - ubuntu-24.04 clang++-18
Process completed with exit code 143.
|
Self Vendored STL - ubuntu-24.04 g++-14
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
Self Vendored STL - ubuntu-24.04 g++-14
Process completed with exit code 143.
|
Ubuntu - ubuntu-20.04 Release
Process completed with exit code 8.
|
Fuzzing
Process completed with exit code 2.
|
gwp-asan (ubuntu-24.04, RelWithDebInfo)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
gwp-asan (ubuntu-24.04, RelWithDebInfo)
Process completed with exit code 143.
|
Ubuntu - ubuntu-24.04-arm Debug
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
Ubuntu - ubuntu-24.04-arm Debug
Process completed with exit code 143.
|
Ubuntu - ubuntu-24.04 Debug with pthread destructors
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
Ubuntu - ubuntu-24.04 Debug with pthread destructors
Process completed with exit code 143.
|
Ubuntu - ubuntu-22.04 Debug C++17
Process completed with exit code 8.
|
Ubuntu - ubuntu-22.04 Debug
Process completed with exit code 8.
|
Ubuntu - ubuntu-20.04 Debug C++17
Process completed with exit code 8.
|
Ubuntu - ubuntu-20.04 Debug
Process completed with exit code 8.
|
Ubuntu - ubuntu-20.04 Debug clang-10 (with pthread destructors).
Process completed with exit code 8.
|
Ubuntu - ubuntu-24.04 Debug
Process completed with exit code 8.
|
Ubuntu - ubuntu-24.04 Debug
Process completed with exit code 8.
|
gwp-asan (ubuntu-24.04, Debug)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
gwp-asan (ubuntu-24.04, Debug)
Process completed with exit code 143.
|
gwp-asan (ubuntu-24.04-arm, Debug)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
gwp-asan (ubuntu-24.04-arm, Debug)
Process completed with exit code 143.
|
Ubuntu - ubuntu-20.04 Release Traced Build
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Ubuntu - ubuntu-20.04 Release clang-10 libstdc++ (Build only)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Crossbuild - Release cross-build for powerpc64le-linux-gnu
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Crossbuild - Debug cross-build for powerpc64le-linux-gnu
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Ubuntu - ubuntu-20.04 Release
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Ubuntu - ubuntu-20.04 Debug C++17
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Ubuntu - ubuntu-20.04 Debug
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
Ubuntu - ubuntu-20.04 Debug clang-10 (with pthread destructors).
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|