First overnight stress campaign, 2026-11-06/07

nRF5340 DK application core, 20 adapters (19 library configurations + the negative control), overnight.sh for 8 hours, 21:52–05:55 UTC. Harness development, not published results. ⚠ pxq RingBuffer_PackedState is the project owner's library (principle 6). Raw report: 2026-11-07-overnight-campaign-raw.md; the JSON records stay on lib-lab1 in ~/lab-runs/overnight-20261106T215245Z/.

Result

The 8 runs that do not count

5 invalid runs: all block mode at the slowest interrupt rate (prescaler 4, an interrupt every 2 560–10 688 cycles). At that rate the buffer stayed empty in ISR → main and full in main → ISR, so the control's bugs never had a chance to show (0 control errors). The validity rule did its job: these runs show nothing either way and were not counted.

3 unfinished runs: all single bytes, fastest interrupts (160–668 cycles), instruction cache off. Re-running that setting and reading the progress after 2 and 4 minutes showed starvation, not a hang in a library: e.g. lwrb ISR → main had moved 30 820 bytes under 3.35 million interrupts, with the buffer found full 3.32 million times: with the cache off its interrupt handler takes about as long as the interrupt period, leaving the main loop almost no CPU time. Not a library defect: a test setting with more than 100 % interrupt load.

Changes made after this campaign

Limits

One core (interrupt vs main loop), one compiler (arm-none-eabi-gcc 14.2.1, -O2), one board. 0 errors over many runs makes hidden ordering bugs of this kind unlikely for these configurations; it does not prove their absence. GenMC found the diffstorm defects that this test cannot see (see ../verify/findings).