What problem does it solve?
Reproducing OpenBSD-specific ponyc build and test failures normally requires GitHub Actions CI runs, and hand-rolling an OpenBSD VM is error-prone due to cloud-init seed setup, doas configuration, disklabel partitioning, and datasize limits.
Core Features & Use Cases
- CI-matched VM provisioning: Boots a cloud-init-configured OpenBSD 7.9 qcow2 image under QEMU/KVM with a cidata seed CD-ROM, passwordless doas, and ssh key access, mirroring the tier-3 CI job.
- Build environment setup: Partitions and mounts a dedicated /build data disk, raises the datasize limit to 4096M for the LLVM build, and installs build dependencies via pkg_add.
- Detached build and test workflow: Syncs the ponyc checkout with rsync, runs the multi-hour LLVM libs build detached with log polling, then configures, builds, and runs the ci-core test suite.
- Use Case: A contributor hits an OpenBSD-only static-PIE linking failure in CI and needs a local VM to reproduce, debug, and validate the fix without pushing to GitHub Actions.
Quick Start
Ask the assistant to set up a local OpenBSD VM for building and testing ponyc using this skill, starting from the prerequisite check.