Skip to content

guard MapDestination destructor against exception from finalize #1572

guard MapDestination destructor against exception from finalize

guard MapDestination destructor against exception from finalize #1572

Triggered via push June 15, 2026 19:57
Status Success
Total duration 23m 27s
Artifacts 12

build-test.yml

on: push
Matrix: build
Test Report
5s
Test Report
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
build (macos-latest, clang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. 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/
build (macos-latest, clang)
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.
build (macos-latest, clang)
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.
build (windows-2022, msvc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2, ilammy/msvc-dev-cmd@v1. 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/
build (windows-2022, msvc)
Saving cache failed: Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
build (ubuntu-latest, clang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. 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/
build (windows-2022, clang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. 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/
build (ubuntu-latest, gcc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. 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/
build (windows-2022, gcc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. 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/

Artifacts

Produced during runtime
Name Size Digest
debug-clang-mmapper-26-06-0-21-g36e80ba8-Linux-x86_64-deb
164 MB
sha256:3f63deb21b14265bc5c816daa4dc2572687f9eaae429b2278cf2a2fd958d6fe7
debug-clang-mmapper-26-06-0-21-g36e80ba8-Windows-x64
188 MB
sha256:6d12c1b69dd7e3b962fb3f246bf0b13917d77b51b8f87c5b2d1c012cf99a8ce6
debug-gcc-mmapper-26-06-0-21-g36e80ba8-Linux-x86_64-deb
219 MB
sha256:e405c85b4ac0ffde24bf7ed82b56e14d7fe91528815a6bb1425fdda1256834f8
debug-gcc-mmapper-26-06-0-21-g36e80ba8-Windows-x64
223 MB
sha256:f8f04661072bada0545522844e18dea04e1afd6ba52199b57d5dd39e13247d57
debug-mmapper-26-06-0-21-g36e80ba8-Mac-arm64-dmg
195 MB
sha256:efb472f644c9a2267da0f2fb3abbddc226db51f394bd9aec0adbbd178c1abcfa
debug-msvc-mmapper-26-06-0-21-g36e80ba8-Windows-x64
175 MB
sha256:8936a17e2e48163e4b5045fdddb783fa5efcc3c26a0a87fcc343c90af97978ba
test-results macos-latest clang
2.17 KB
sha256:a3d4ef9c9333e2f4ee2834b8bd72e5816d65a7dd680af297caf23e0e2cbdd718
test-results ubuntu-latest clang
2.16 KB
sha256:c0eeca09e067ad6b28370c3e0ac076c02ea17f1dffa42e4d5752c37add3fe138
test-results ubuntu-latest gcc
2.17 KB
sha256:b94dfc21ebdd3b68668a4358f68f186df67aa5db3c91346f4fd5a48fde4c079d
test-results windows-2022 clang
595 Bytes
sha256:f16f307fa1dbe0fe8cb5ba4ce82e6cfcfbd35ee537b8e7cb1e06c20e90ba1f1c
test-results windows-2022 gcc
599 Bytes
sha256:844020fdd8f36b1a91e23eb31765d8019f43b894fa01eb0961c1a83fc6fcad66
test-results windows-2022 msvc
594 Bytes
sha256:ca34998cac470ee331f9845d941bd3da1ba81bc58dd1c9913b420444dfb0a72a