On 09/11/2023 3:49 pm, Anthony PERARD wrote: > Currently, the test rely on QEMU and Xen finishing the boot in under > two seconds. That's both very long and very short. Xen usually managed > to print "All set up" under a second. Unless for some reason we try to > run the test on a machine that's busy doing something else. > > Rework the test to exit as soon as Xen is done. > > There's two `tail -f`, the first one is there simply to monitor test > progress in GitLab console. The second one is used to detect the test > result as soon as QEMU add it to the file. Both `tail` exit as soon as > QEMU exit. > > If QEMU fails at start, and exit early, both `tail` will simply exit, > resulting in a failure. > > If the line we are looking for is never printed, the `timeout` on the > second `tail` will force the test to exit with an error. > > Signed-off-by: Anthony PERARD <[email protected]>
Looks plausible, but all these qemu-smoke scripts are pretty similar, and copied from one-another. We should make this change consistently to all testing (there's nothing RISC-V specific about why this test is failing on this runner), and it would be really nice if we could try to make it a bit more common than it currently is. ~Andrew
