Hi,
I finally got the rumprun test suite running today; the final problem
was, *ahem*, me having broken pthread_cond_timedwait() for rumprun/xen a
week ago, and for a long time I incorrectly thought that the test
framework is buggy ...
After a build, you can run the tests by going to ./tests and running
"./runtests.sh {qemu,xen}", depending on if you built baremetal or xen.
Travis already runs the tests for baremetal, but since we can't start
Xen guests there, /xen is not tested that way. I'm assuming Justin's
buildbot will start running the xen tests, perhaps also the Xen
project's osstest.
The results are communicated using disk images, which seemed like the
most universal way to pass data between backgrounded & monitored guests
and the test control host.
Of course a few more test cases would be nice, though I think that even
the current, extremely modest number of tests provide a nice
"ping-test", which show that quite a few things are actually working.
- antti
