v4 fabric to spec: the mesh boot, the one adaptive heartbeat, mechanism A (#189) #197
@@ -45,13 +45,13 @@ milestone, #156): what v4 needs of it, the block layer, moves into v4 and the re
|
||||
| Bare metal | a generic PC (amd64; first on the bench: a Beelink SER5), Raspberry Pi 5 (aarch64), Milk-V Mars (riscv64); Zynq-7020 (ARMv7) not yet ported | Images build; first boots on the bench — `boards/BRINGUP.md` |
|
||||
|
||||
**v4 is the default build, and v3 is being retired**: every kernel boots v4 unless its boot
|
||||
arguments say `system=v3`. POST at boot, on all three ISAs: v4 — **538 tests**,
|
||||
`PARITY:V4_SYSTEM word_count=317 dict_hash=0xfec8c47cfc6f437f`; v3 — **1052 tests**,
|
||||
arguments say `system=v3`. POST at boot, on all three ISAs: v4 — **990 tests**,
|
||||
`PARITY:V4_SYSTEM word_count=403 dict_hash=0x627f392ccbaa96f1` (`logs/20261117-222402/PROTOCOL.md`); v3 — **1052 tests**,
|
||||
`PARITY:M7.1a word_count=526 hash=0x82f4ae7cb2e2d424`.
|
||||
|
||||
**How a change gets in** (the Captain Bob method): `master` is reached only through a pull request
|
||||
that passed **acceptance** — amd64, aarch64 and riscv64 booted in QEMU to `[zuse@Hera] ok>`, POST
|
||||
538/538 and one `dict_hash` on all three; the PC stick booted loaded above 2 GiB, as a PC's firmware
|
||||
990/990 and one `dict_hash` on all three; the PC stick booted loaded above 2 GiB, as a PC's firmware
|
||||
loads it; and the 32-bit build's tests. Every acceptance boot starts from a fresh stick, so every
|
||||
run is a first boot. The same stages run nightly and for every release (`scripts/nightly.sh`); the
|
||||
serial logs are committed.
|
||||
|
||||
Reference in New Issue
Block a user