Build nodes

The machines that build and check DUR's packages, each build in a throwaway VM of its own. Their state comes from the build server whenever it changes.

NodeStateStrengthBuilds ArchitecturesDebusine30 days
daemonratte1
large
building
mmdebstrap, since 2026-11-21T13:59
connected since 2026-11-21 13:59
12 CPUs, 62.8 GiB everything, also browsers, kernels, LibreOffice amd64, i386
emulated: arm64, armhf, ppc64el, riscv64
0.16.2 104 built, 198 failed
durnode2-test idle
connected since 2026-11-21 12:39
2 CPUs, 2.8 GiB small packages amd64, i386
emulated: arm64, armhf, ppc64el, riscv64
0.16.2 72 built, 4 failed
durnode3-test
large
building
mmdebstrap, since 2026-11-21T13:59
connected since 2026-11-21 13:59
12 CPUs, 9.7 GiB everything, also browsers, kernels, LibreOffice amd64, i386
emulated: arm64, armhf, ppc64el, riscv64
0.16.2 1 built, 1 failed

Large nodes (32 GiB of memory and room for big builds, marked by an admin or a moderator who may) also get browsers, kernels and LibreOffice. Other architectures run emulated (qemu-user), which is slow.