Skip to content

Update estimate_gaussian_parameters_2d template function implementation #843

Update estimate_gaussian_parameters_2d template function implementation

Update estimate_gaussian_parameters_2d template function implementation #843

Triggered via push June 7, 2026 01:36
Status Failure
Total duration 1d 0h 0m 2s
Artifacts

snap.yml

on: push
Linux x86 (Snap Publish)
1h 7m
Linux x86 (Snap Publish)
Linux x86 (GCC 15.2.0 Source)
35m 5s
Linux x86 (GCC 15.2.0 Source)
Linux x86 (GCC 15.2.0 - Local Machine)
1d 0h
Linux x86 (GCC 15.2.0 - Local Machine)
Linux x86 (Perf Profiling)
1h 5m
Linux x86 (Perf Profiling)
macOS (GCC 14)
1h 11m
macOS (GCC 14)
Windows (MSVC)
49m 28s
Windows (MSVC)
Linux ARM64 (QEMU)
5m 21s
Linux ARM64 (QEMU)
Fit to window
Zoom out
Zoom in

Annotations

6 errors, 5 warnings, and 1 notice
Linux ARM64 (QEMU)
The process '/home/runner/work/_actions/uraimo/run-on-arch-action/v2/src/run-on-arch.sh' failed with exit code 2
Linux x86 (GCC 15.2.0 Source)
Process completed with exit code 143.
Windows (MSVC)
Process completed with exit code 1.
Linux x86 (Perf Profiling)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Linux x86 (Snap Publish)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Linux x86 (GCC 15.2.0 - Local Machine)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Linux ARM64 (QEMU)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, uraimo/run-on-arch-action@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Linux x86 (GCC 15.2.0 Source)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Windows (MSVC)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
macOS (GCC 14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
macOS (GCC 14)
The following taps are not trusted: aws/tap azure/bicep hashicorp/tap 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 brew trust --formula hashicorp/tap/packer You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep hashicorp/tap Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep hashicorp/tap 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 (MSVC)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026