Bump the github-actions group across 1 directory with 5 updates

[dependabot]

Bumps the github-actions group with 5 updates in the / directory:

Package	From	To
docker/setup-buildx-action	4.2.0	4.3.0
bencherdev/bencher	0.6.11	0.6.12
vmactions/freebsd-vm	1.5.3	1.5.5
vmactions/netbsd-vm	1.4.6	1.4.7
vmactions/openbsd-vm	1.4.6	1.4.7

Updates docker/setup-buildx-action from 4.2.0 to 4.3.0

Release notes

Sourced from docker/setup-buildx-action's releases.

v4.3.0

• Bump @​docker/actions-toolkit from 0.92.0 to 0.95.0 in docker/setup-buildx-action#595
• Bump brace-expansion from 1.1.13 to 1.1.18 in docker/setup-buildx-action#600
• Bump js-yaml from 5.2.0 to 5.3.0 in docker/setup-buildx-action#585
• Bump postcss from 8.5.10 to 8.5.25 in docker/setup-buildx-action#598
• Bump undici from 6.27.0 to 6.28.0 in docker/setup-buildx-action#601

Full Changelog: docker/setup-buildx-action@v4.2.0...v4.3.0

Commits

• 37fe631 Merge pull request #595 from docker/dependabot/npm_and_yarn/docker/actions-to...
• b5c4f91 [dependabot skip] chore: update generated content
• 3e93b63 build(deps): bump @​docker/actions-toolkit from 0.92.0 to 0.95.0
• e527031 Merge pull request #600 from docker/dependabot/npm_and_yarn/brace-expansion-1...
• c68814b [dependabot skip] chore: update generated content
• 3f891b0 build(deps): bump brace-expansion from 1.1.13 to 1.1.18
• 787db26 Merge pull request #585 from docker/dependabot/npm_and_yarn/js-yaml-5.2.1
• f779368 [dependabot skip] chore: update generated content
• 7d5e604 build(deps): bump js-yaml from 5.2.0 to 5.3.0
• 292c2fb Merge pull request #590 from docker/dependabot/github_actions/actions/setup-n...
• Additional commits viewable in compare view

Updates bencherdev/bencher from 0.6.11 to 0.6.12

Release notes

Sourced from bencherdev/bencher's releases.

v0.6.12

• Support Gungraun JSON format (Thank you gamma0987)

Commits

• 8d75325 Release v0.6.12
• eff31e6 Run the Console against the dev API without a local API (#981)
• 214a7c8 Remove Netlify from the console deploy path (#975)
• a5cf93a Support gungraun json format (#962)
• 8fe6262 Add exacb, zkbenchmarks, babybear-labs, LITA, and Aerospike to Prior Art (#974)
• 6a0a885 Deploy the prod console to Cloudflare Workers (#973)
• 408b45c Bump Litestream from 0.5.13 to 0.5.16 (#966)
• b61d333 Authenticate the console smoke test with a secret header (#968)
• 9e9dfed Restore the Cloudflare console adapter files (#969)
• 13a240a Deploy the dev console to Cloudflare Workers (#965)
• Additional commits viewable in compare view

Updates vmactions/freebsd-vm from 1.5.3 to 1.5.5

Release notes

Sourced from vmactions/freebsd-vm's releases.

v1.5.5

The runtime moves to anyvm v0.6.5 (from v0.6.4), keeping the whole fleet on one version. This action's surface is unchanged -- same images, same sync methods, same defaults. The bump carries one runtime change of note: on hosts whose nested AMD virtualization corrupts AVX512 XSAVE state, the CPU-feature mask now drops the whole AVX512 family instead of only avx512f.

Full Changelog: vmactions/freebsd-vm@v1.5.4...v1.5.5

v1.5.4

sync: tar

A fourth way to share the workspace, available on every architecture including riscv64 and powerpc64, where rsync and sshfs do not exist:

The workspace is streamed in as a ustar archive over the ssh connection the action already opens, and streamed back the same way when the run finishes. Nothing is installed in the guest and no filesystem support is needed on either side, unlike sshfs and nfs. Verified before shipping: 300 files plus a 1 MB binary blob pushed into a 15.1 guest, a file written inside it, the whole tree pulled back and compared by content hash.

rsync remains the default. Reach for tar when the guest lacks rsync, or when a mount-based method is more machinery than the job needs.

Under the hood

The image builder moves to freebsd-builder v2.2.6 and the runtime to anyvm v0.6.4, nine releases on from what v1.5.3 shipped. Most of that is other guests, but two fixes reach every action:

A failed folder sync used to be a warning. The run continued with the guest missing the files it was about to use, which surfaced much later as a confusing error or a job that sat until its timeout. It is now fatal, and says so.

The workspace push no longer carries the runner's own harness directories into the guest.

Also

The shell note no longer mentions usesh, which has not been needed for some time.

Full Changelog: vmactions/freebsd-vm@v1.5.3...v1.5.4

Commits

• f0552d3 Update vmactions/freebsd-vm from base-vm
• 5595fc6 Generated from base-vm
• 0206b2a Sync from base-builder
• 2ed1747 Update vmactions/freebsd-vm from base-vm
• be1c6e8 Generated from base-vm
• bddcfce Update vmactions/freebsd-vm from base-vm
• 139a2cb Generated from base-vm
• 0a1a391 Update version to v1.5.4
• 759dd0c Update vmactions/freebsd-vm from base-vm
• b5370dd Generated from base-vm
• Additional commits viewable in compare view

Updates vmactions/netbsd-vm from 1.4.6 to 1.4.7

Release notes

Sourced from vmactions/netbsd-vm's releases.

v1.4.7

sync: tar

A new way to share the workspace: the tree is streamed in as a ustar archive over the ssh connection the action already opens, and streamed back the same way when the run finishes. Nothing is installed in the guest and no filesystem support is needed on either side, unlike sshfs and nfs. netbsd-builder v2.2.3 declares it for every release conf -- including the images that ship no rsync at all, where tar is the first stream-based option. Verified on this guest before the declaration went in: 300 files plus a 1 MB binary blob pushed, a file written inside the VM, the whole tree pulled back and compared by content hash.

rsync remains the default where the image ships it.

Under the hood

netbsd-builder v2.2.3 also sets the guest hostname consistently across releases and architectures.

The runtime moves to anyvm v0.6.5, ten releases on from the v0.5.5 that v1.4.6 shipped. Two of its fixes reach every job: a failed folder sync is now fatal instead of a warning that left the guest running without the files it was about to use, and the workspace push no longer carries the runner's own harness directories into the guest.

Full Changelog: vmactions/netbsd-vm@v1.4.6...v1.4.7

Commits

• 6334c83 Update vmactions/netbsd-vm from base-vm
• 9ec6efa Generated from base-vm
• 9eab485 Sync from base-builder
• 99223e1 Update vmactions/netbsd-vm from base-vm
• 68b595d Generated from base-vm
• 561fd2e Update version to v1.4.6
• b7b1f33 Update vmactions/netbsd-vm from base-vm
• 81a85b6 Generated from base-vm
• f960a54 Bump versions from upstream releases
• d0be540 Update vmactions/netbsd-vm from base-vm
• Additional commits viewable in compare view

Updates vmactions/openbsd-vm from 1.4.6 to 1.4.7

Release notes

Sourced from vmactions/openbsd-vm's releases.

v1.4.7

sync: tar

A new way to share the workspace, available on every architecture: the tree is streamed in as a ustar archive over the ssh connection the action already opens, and streamed back the same way when the run finishes. Nothing is installed in the guest and no filesystem support is needed on either side, unlike sshfs and nfs. openbsd-builder v2.1.0 declares it for every release, and it was verified on this guest before the declaration went in: 300 files plus a 1 MB binary blob pushed, a file written inside the VM, the whole tree pulled back and compared by content hash.

rsync remains the default.

Under the hood

openbsd-builder v2.1.0 is also the first openbsd build to publish releases.json, the machine-readable index this action bakes its configuration from -- which is why the pre-tar method list survived until now.

The runtime moves to anyvm v0.6.5, ten releases on from the v0.5.5 that v1.4.6 shipped. Two of its fixes reach every job: a failed folder sync is now fatal instead of a warning that left the guest running without the files it was about to use, and the workspace push no longer carries the runner's own harness directories into the guest.

Full Changelog: vmactions/openbsd-vm@v1.4.6...v1.4.7

Commits

• 86cdc08 Update vmactions/openbsd-vm from base-vm
• 4d73785 Generated from base-vm
• e327e92 Sync from base-builder
• 533018c Update vmactions/openbsd-vm from base-vm
• 222bcdb Generated from base-vm
• 73697f6 Update vmactions/openbsd-vm from base-vm
• e334303 Generated from base-vm
• a824726 Update version to v1.4.6
• 8ddee6b Update vmactions/openbsd-vm from base-vm
• 3c73357 Generated from base-vm
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

Coverage report (cross-platform merged)

Lines covered (src/snmalloc/**): 2822 / 3179 (88.77%)

Merged line coverage is the per-line union across all platforms. Region coverage is reported per-platform only; no cross-platform region total is computed.

Per-directory breakdown

Directory	Lines covered	Lines executable	%
src/snmalloc/stl	2	4	50.00%
src/snmalloc/override	94	156	60.26%
src/snmalloc/pal	343	449	76.39%
src/snmalloc/mitigations	14	18	77.78%
src/snmalloc/aal	52	60	86.67%
src/snmalloc/ds_core	349	399	87.47%
src/snmalloc/global	266	303	87.79%
src/snmalloc/ds	328	357	91.88%
src/snmalloc/backend_helpers	336	356	94.38%
src/snmalloc/mem	840	872	96.33%
src/snmalloc/ds_aal	108	112	96.43%
src/snmalloc/backend	90	93	96.77%

Per-platform contributions (advisory)

Platform	Lines covered	Lines executable	Lines %	Regions covered	Regions executable	Regions %
freebsd-14	4268	4725	90.33%	3855	5677	67.91%
linux-self-host-shim-checks	4437	4889	90.75%	4084	6136	66.56%
linux-self-host-shim-checks-selfhost	1640	2323	70.60%	1500	2913	51.49%
macos-14	4255	4693	90.67%	3885	5691	68.27%
windows-2022	4177	4712	88.65%	3834	5653	67.82%