Skip to content

Hunter: Use GetPointsInRadius() instead of square #2626

Hunter: Use GetPointsInRadius() instead of square

Hunter: Use GetPointsInRadius() instead of square #2626

Re-run triggered June 18, 2026 11:46
Status Failure
Total duration 21m 24s
Artifacts

unit-tests.yml

on: pull_request
Matrix: Linux
Matrix: Windows
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 6 warnings
Windows (windows-2022, Visual Studio 17 2022, Release, x64)
Process completed with exit code 1.
Windows (windows-2022, Visual Studio 17 2022, Release, Win32)
The strategy configuration was canceled because "Windows.windows-2022_Visual_Stu_4" failed
Windows (windows-2022, Visual Studio 17 2022, Release, Win32)
The operation was canceled.
Linux (gcc-11, ubuntu-22.04, RelWithDebInfo, 4.1.1, 1.74.0)
Process completed with exit code 8.
Linux (clang, macos-14, Debug)
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
Linux (clang, macos-14, Debug)
The following taps are not trusted: aws/tap azure/bicep Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
Windows (windows-2022, Visual Studio 17 2022, Debug, x64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: MarkusJx/install-boost@8ba8b2fac59ef3d91a838bb4aa53ceabd33d1aa3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Windows (windows-2022, Visual Studio 17 2022, Debug, Win32)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: MarkusJx/install-boost@8ba8b2fac59ef3d91a838bb4aa53ceabd33d1aa3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Windows (windows-2022, Visual Studio 17 2022, Release, x64)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: MarkusJx/install-boost@8ba8b2fac59ef3d91a838bb4aa53ceabd33d1aa3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Windows (windows-2022, Visual Studio 17 2022, Release, Win32)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: MarkusJx/install-boost@8ba8b2fac59ef3d91a838bb4aa53ceabd33d1aa3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/