14328 2021-03-25 15:35:02 +0000 Mitigate AB ptest intermittent failure 2021-05-20 15:13:45 +0000 1 1 10 QA/Testing Package Testing (ptest) ptest unspecified x86 Multiple RESOLVED FIXED AB-INT Medium+ normal 3.4 M1 14163 1 yf3yu richard.purdie alexandre.belloni randy.macleod --- --- Don't know oldest_to_newest 89768 0 yf3yu 2021-03-25 15:35:02 +0000 It feels like an I/O load issue, work on some sort of `flock`/`dd` timeout is currently done to try to get to the bottom of the cause and verify if it is indeed I/O related. 2 solutions have been suggested in the Mar 25 triage IIRC they were: * cgroups control to give qemu an advantage over builds * nice levels to make qemu higher priority (lowering the builds priority) 89841 1 randy.macleod 2021-04-01 14:35:24 +0000 We were doing this anyway but this bug can be used to track things. 89944 2 richard.purdie 2021-04-15 13:35:10 +0000 Most autobuilder workers only have cgroups v1 which doesn't give the IO controls we'd need. We already set ionice/nice levels. The ionice level doesn't affect async writes. We've now added support for running qemu images within tmpfs. 89958 3 alexandre.belloni 2021-04-15 14:58:58 +0000 Following the triage call, it seems necessary to: - timestamp the start and end of the image copy to tmpfs - double the qemu start timeout 90431 4 randy.macleod 2021-05-20 15:13:32 +0000 Many changes including: - moving the qemu rootfs to tmpfs - limiting glibc self-test memory usage - adding smp to qemu image for x86, arm and changing the x86 target machine. and likely more have improve ptests. Closing this generic bug. Open specific issues for additional problems. 90432 5 randy.macleod 2021-05-20 15:13:45 +0000 As per previous comment.