On Thu, 2022-12-01 at 11:27 +0100, Alexander Kanavin wrote:
On Wed, 30 Nov 2022 at 14:15, Richard Purdie
* We need to have a 32 bit ptest run on the autobuilder (qemux86 shouldI just ran qemux86 full ptest locally. It took 4h:10m (same as
work, not sure we can make qemuarm fast). Whether this is manually
triggered, not sure. We could have a smaller set of ptests to run for
qemuarm64 ptest on an arm worker). The fails were:
So I think we could as well fix these, and add full qemux86 ptest to
a-full? It is not heavy on the builder machine (mostly just runs a
single qemu thread), it's just long.
I think we should fix those and we should add the target to the
autobuilder but I'm reluctant to add a long test to a-full. The fact it
is relatively clean suggests it doesn't regress that often. We could do
something like a once a month trigger for it?