What problem does it solve?
Reproducing FreeBSD-specific ponyc bugs is hard without a matching environment: the tier-3 CI job exercises paths (embedded-LLD static linking, sanitizer links, dtrace providers, base libc++/libunwind) that Linux clang jobs never touch, and hand-rolling a FreeBSD VM hits pitfalls like cloud-init seed setup, root bootstrap via expect, and missing bash in the base system.
Core Features & Use Cases
- CI-matched VM provisioning: Downloads the FreeBSD BASIC-CLOUDINIT image, builds a cloud-init seed with your SSH key, and boots a daemonized QEMU/KVM (or HVF on macOS) VM matching the ponyc tier-3 CI configuration.
- One-time root bootstrap: Uses expect to drive su and install build dependencies (cmake, gmake, libunwind, doas) with passwordless doas for the freebsd user.
- Build and test workflow: Rsyncs your ponyc checkout into the VM, runs the multi-hour detached LLVM libs build, then builds and tests ponyc with CMake presets and ctest.
- Use Case: A contributor hits a FreeBSD-only link failure in CI. They use this Skill to stand up a local FreeBSD 15.1 VM, rsync their fix branch, rebuild, and run the ci-core test suite plus the sanitizer and dtrace smoke scripts to validate the fix before pushing.
Quick Start
Ask the AI to set up a local FreeBSD VM matching ponyc tier-3 CI so you can reproduce and debug a FreeBSD-specific ponyc build issue.