Skip to content

Update frametest.cpp #3844

Update frametest.cpp

Update frametest.cpp #3844

Triggered via push November 14, 2024 16:41
Status Failure
Total duration 27m 33s
Artifacts

build.yml

on: push
Matrix: build
Update manifest file on download server
33s
Update manifest file on download server
Fit to window
Zoom out
Zoom in

Annotations

23 errors and 6 warnings
Windows 2019 (MSVC): src/test/frametest.cpp#L15
syntax error: missing ';' before 'switch'
Windows 2019 (MSVC): src/test/frametest.cpp#L15
'reinterpret_cast': cannot convert from 'double' to '__int64 *'
Windows 2019 (MSVC): src/test/frametest.cpp#L15
'testing::internal::EqHelper::Compare': function does not take 3 arguments
Windows 2019 (MSVC): src/test/frametest.cpp#L15
'gtest_ar': const object must be initialized
Windows 2019 (MSVC)
Process completed with exit code 1.
macOS 12 x64
expected ';' at end of declaration
macOS 12 x64
expected expression
macOS 12 x64
Process completed with exit code 1.
macOS 12 arm64
expected ';' at end of declaration
macOS 12 arm64
expected expression
macOS 12 arm64
Process completed with exit code 1.
Ubuntu 22.04 (gcc): src/test/frametest.cpp#L15
expected ‘,’ or ‘;’ before ‘switch’
Ubuntu 22.04 (gcc): src/test/frametest.cpp#L15
expected ‘}’ before ‘else’
Ubuntu 22.04 (gcc): src/test/frametest.cpp#L13
unused variable ‘inf’ [-Werror=unused-variable]
Ubuntu 22.04 (gcc): src/test/frametest.cpp#L15
‘gtest_ar’ was not declared in this scope
Ubuntu 22.04 (gcc): src/test/frametest.cpp#L17
expected declaration before ‘}’ token
Ubuntu 22.04 (gcc)
Process completed with exit code 2.
Ubuntu 22.04 (Qt 6.2, gcc): src/test/frametest.cpp#L15
expected ‘,’ or ‘;’ before ‘switch’
Ubuntu 22.04 (Qt 6.2, gcc): src/test/frametest.cpp#L15
expected ‘}’ before ‘else’
Ubuntu 22.04 (Qt 6.2, gcc): src/test/frametest.cpp#L13
unused variable ‘inf’ [-Werror=unused-variable]
Ubuntu 22.04 (Qt 6.2, gcc): src/test/frametest.cpp#L15
‘gtest_ar’ was not declared in this scope
Ubuntu 22.04 (Qt 6.2, gcc): src/test/frametest.cpp#L17
expected declaration before ‘}’ token
Ubuntu 22.04 (Qt 6.2, gcc)
Process completed with exit code 2.
macOS 12 x64
A brownout will take place on November 11, 14:00 UTC - November 12, 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
macOS 12 x64
ninja 1.12.1 is already installed and up-to-date. To reinstall 1.12.1, run: brew reinstall ninja
macOS 12 x64
You are using macOS 12. We (and Apple) do not provide support for this old version. It is expected behaviour that some formulae will fail to build in this old version. It is expected behaviour that Homebrew will be buggy and slow. Do not create any issues about this on Homebrew's GitHub repositories. Do not create any issues even if you think this message is unrelated. Any opened issues will be immediately closed without response. Do not ask for help from Homebrew or its maintainers on social media. You may ask for help in Homebrew's discussions but are unlikely to receive a response. Try to figure out the problem yourself and submit a fix as a pull request. We will review it but may or may not accept it.
macOS 12 arm64
A brownout will take place on November 11, 14:00 UTC - November 12, 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
macOS 12 arm64
ninja 1.12.1 is already installed and up-to-date. To reinstall 1.12.1, run: brew reinstall ninja
macOS 12 arm64
You are using macOS 12. We (and Apple) do not provide support for this old version. It is expected behaviour that some formulae will fail to build in this old version. It is expected behaviour that Homebrew will be buggy and slow. Do not create any issues about this on Homebrew's GitHub repositories. Do not create any issues even if you think this message is unrelated. Any opened issues will be immediately closed without response. Do not ask for help from Homebrew or its maintainers on social media. You may ask for help in Homebrew's discussions but are unlikely to receive a response. Try to figure out the problem yourself and submit a fix as a pull request. We will review it but may or may not accept it.