Skip to content
CI

Implement non-fragmenting component storage #7677

# to view logs

Implement non-fragmenting component storage

Implement non-fragmenting component storage #7677

Triggered via push February 15, 2025 02:04
@SanderMertensSanderMertens
pushed e137981
non_fragmenting_components
Status Failure
Total duration 16m 56s
Artifacts –

ci.yml

on: push
build-linux
19s
build-linux
build-macos
26s
build-macos
build-windows
4m 27s
build-windows
typos
5s
typos
Matrix: build-msys
Matrix: test-msys
build-meson
10s
build-meson
build-bazel-linux
2m 17s
build-bazel-linux
test-amalgamated
17s
test-amalgamated
build-scan-build
4m 13s
build-scan-build
Matrix: build-amalgamated
Matrix: build-custom
Matrix: build
Matrix: test-cpp-unix
Matrix: test-os-alloc-core
Matrix: test-sanitized-addons
Matrix: test-sanitized-collections
Matrix: test-sanitized-core
Matrix: test-sanitized-cpp
Matrix: test-sanitized-meta
Matrix: test-sanitized-query
Matrix: test-sanitized-script
Matrix: build-cmake
Matrix: test-c-unix
Matrix: test-cmake
Matrix: test-cpp-macos
build-bazel-windows
4m 41s
build-bazel-windows
test-windows
1m 25s
test-windows
Matrix: build-cmake-windows
Fit to window
Zoom out
Zoom in

Annotations

32 errors and 24 warnings
test-cpp-unix (ubuntu-22.04, gcc-11, g++-11)
Process completed with exit code 255.
build-bazel-linux
Process completed with exit code 3.
test-msys (clang64, clang, clang++)
Process completed with exit code 127.
test-cpp-macos (macos-14, 15.4)
Process completed with exit code 255.
test-sanitized-core (ubuntu-20.04)
Process completed with exit code 255.
test-cmake (macos-latest)
Process completed with exit code 8.
test-msys (mingw32, gcc, g++)
Process completed with exit code 127.
test-msys (mingw64, gcc, g++)
Process completed with exit code 127.
test-cpp-macos (macos-13, 14.3.1)
Process completed with exit code 255.
test-msys (ucrt64, gcc, g++)
Process completed with exit code 127.
test-cpp-macos (macos-15, 16.0)
Process completed with exit code 255.
build-scan-build
Process completed with exit code 1.
test-os-alloc-core (ubuntu-20.04)
Process completed with exit code 255.
test-windows
Process completed with exit code 1.
test-cpp-unix (ubuntu-24.04, gcc-13, g++-13)
Process completed with exit code 255.
test-c-unix (macos-13)
Process completed with exit code 255.
test-cmake (macos-13)
Process completed with exit code 8.
test-c-unix (macos-latest)
Process completed with exit code 255.
test-cpp-unix (ubuntu-latest, clang-14, clang++-14)
Process completed with exit code 255.
test-cpp-unix (ubuntu-latest, gcc-12, g++-12)
Process completed with exit code 255.
test-cpp-unix (ubuntu-latest, clang-15, clang++-15)
Process completed with exit code 255.
build-bazel-windows
Process completed with exit code 1.
test-c-unix (ubuntu-latest)
Process completed with exit code 255.
test-cpp-unix (ubuntu-20.04, clang-10, clang++-10)
Process completed with exit code 255.
test-cpp-unix (ubuntu-20.04, clang-11, clang++-11)
Process completed with exit code 255.
test-cmake (ubuntu-latest)
Process completed with exit code 8.
test-cpp-unix (ubuntu-20.04, clang-12, clang++-12)
Process completed with exit code 255.
test-cpp-unix (ubuntu-20.04, gcc-10, g++-10)
Process completed with exit code 255.
test-cpp-unix (ubuntu-20.04, clang-9, clang++-9)
Process completed with exit code 255.
test-cpp-unix (ubuntu-20.04, gcc-9, g++-9)
Process completed with exit code 255.
test-cpp-unix (ubuntu-20.04, clang-8, clang++-8)
Process completed with exit code 255.
test-sanitized-cpp (ubuntu-20.04)
Process completed with exit code 255.
test-sanitized-collections (ubuntu-20.04)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
test-sanitized-addons (ubuntu-20.04)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
test-sanitized-core (ubuntu-20.04)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
test-sanitized-meta (ubuntu-20.04)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
test-sanitized-script (ubuntu-20.04)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
test-os-alloc-core (ubuntu-20.04)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
test-sanitized-query (ubuntu-20.04)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
build (ubuntu-20.04, clang-10, clang++-10)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
build (ubuntu-20.04, clang-11, clang++-11)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
build (ubuntu-20.04, clang-8, clang++-8)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
build (ubuntu-20.04, clang-12, clang++-12)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
test-cpp-unix (ubuntu-20.04, clang-10, clang++-10)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
test-cpp-unix (ubuntu-20.04, clang-11, clang++-11)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
test-cpp-unix (ubuntu-20.04, clang-12, clang++-12)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
test-cpp-unix (ubuntu-20.04, gcc-10, g++-10)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
build (ubuntu-20.04, clang-9, clang++-9)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
test-cpp-unix (ubuntu-20.04, clang-9, clang++-9)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
test-cpp-unix (ubuntu-20.04, gcc-9, g++-9)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
test-cpp-unix (ubuntu-20.04, clang-8, clang++-8)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
build (ubuntu-20.04, gcc-10, g++-10)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
build (ubuntu-20.04, gcc-7, g++-7)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
build (ubuntu-20.04, gcc-8, g++-8)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
test-sanitized-cpp (ubuntu-20.04)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
build (ubuntu-20.04, gcc-9, g++-9)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101