All tests in /usr/src/regress are run every day by cron(8).
The test machines are automatically installed from an i386
or amd64 snapshot, the current source tree is checked out
and necessary packages are installed.
The results are shown over the time in a HTML table.
Complete log output from the setup and test run exist.
Tests are skipped if packages are missing, if they are
specific for another architecture, or if additional remote
machines are missing.
The framework to run everything is available at
OpenBSD cvs checkout performance
An OpenBSD release is installed.
Based on that, the kernel sources for a specific date are
checked out from cvs.
A new kernel is built, installed, and performace tests are
executed with that.
The checkout, build, test is iterated in a loop while
advancing the cvs checkout date in steps.
Currently iperf TCP and UDP, tcpbench TCP and kernel build
times are measured.
To reach over incompatibilities between the kernel and user
land or build enviroment, so called build quirks are used.
Then the necessary parts of the source tree are updated or
After building and installing the relevant tools, checkout
and building kernel continues.
Run make test for selected ports.
Make build and release.
test suite of the
project is designed to find differences in system call
behavior of various POSIX operating systems.
Run the tests during OpenBSD regress and display the results
The date in the table is taken from the snapshot kernel's
open POSIX test
provides good test coverage for system calls.
It tries to compile varoius test programs and runs a lot
The output of the build and run with a current OpenBSD
snapshot is reported.
The test suite is mature and unmaintained, so the result
is not significant.
The important part is that it executes many error paths in
the kernel and libc.
for work time, rack space, hardware, network, and electricity.