Skip to content

TypeHelpers: pre-callocate optionNames even if no names are provided … #1

TypeHelpers: pre-callocate optionNames even if no names are provided …

TypeHelpers: pre-callocate optionNames even if no names are provided … #1

Triggered via push February 19, 2025 00:18
Status Failure
Total duration 1d 7h 54m 2s
Artifacts

ci.yml

on: push
Matrix: Linux
Matrix: OS X
Matrix: Windows
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 10 warnings
OS X (Debug, clang, clang++, macos-12, 3.9)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
OS X (Debug, gcc-11, g++-11, false, macos-11, 3.8)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
OS X (Debug, clang, clang++, true, macos-11, 3.8)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
OS X (Release, clang, clang++, true, macos-11, 3.8)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
OS X (Release, clang, clang++, macos-12, 3.9)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
OS X (Release, gcc-11, g++-11, false, macos-11, 3.8)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
Linux (Debug, clang-12, clang++-12, ubuntu-20.04, 2.7, 3.8)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Linux (Debug, clang-10, clang++-10, ubuntu-20.04, 2.7, 3.8)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Linux (Debug, gcc-10, g++-10, ubuntu-20.04, 2.7, 3.8)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Linux (Debug, gcc-9, g++-9, ubuntu-20.04, 2.7, 3.8)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Linux (Debug, clang-11, clang++-11, ubuntu-20.04, 2.7, 3.8)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Linux (Release, clang-11, clang++-11, ubuntu-20.04, 2.7, 3.8)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Linux (Release, clang-10, clang++-10, ubuntu-20.04, 2.7, 3.8)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Linux (Release, clang-12, clang++-12, ubuntu-20.04, 2.7, 3.8)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Linux (Release, gcc-10, g++-10, ubuntu-20.04, 2.7, 3.8)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Linux (Release, gcc-9, g++-9, ubuntu-20.04, 2.7, 3.8)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101