[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Automated testing of block/gluster.c with upstream Glus
Re: [Qemu-devel] Automated testing of block/gluster.c with upstream Gluster
Tue, 28 Jun 2016 17:20:03 +0200
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
Dne 28.6.2016 v 16:10 Kevin Wolf napsal(a):
Am 28.06.2016 um 11:02 hat Niels de Vos geschrieben:
it seems we broke the block/gluster.c functionality with a recent patch
in upstream Gluster. In order to prevent this from happening in the
future, I would like to setup a Jenkins job that installs a plan CentOS
with its version of QEMU, and nightly builds of upstream Gluster.
Getting a notification about breakage the day after a patch got merged
seems like a reasonable approach.
The test should at least boot the generic CentOS cloud image (slightly
modified with libguestfs) and return a success/fail. I am wondering if
there are automated tests like this already, and if I could (re)use some
of the scripts for it. At the moment, I am thinking to so it like this:
- download the image 
- set kernel parameters to output on the serial console
- add a auto-login user/script
- have the script write "bootup complete" or something
- have the script poweroff the VM
- script that started the VM checks for the "bootup complete" message
- return success/fail
Sounds like something that Avocado should be able (or actually is
designed) to do. I can't tell you the details of how to write the test
case for it, but I'm adding a CC to Lukáš who probably can (and I think
it shouldn't be hard anyway).
yes, Avocado is designed to do this and I believe it even contain quite
a few Gluster tests. You can look for them in avocado-vt or ping our QA
folks who might give you some pointers (cc Xu nad Hao).
Regarding the building the CI I use the combination of Jenkins, Jenkins
job builder and Avocado (avocado-vt) to check power/arm
weekly/per-package-update. Jenkins even supports github and other
triggers if you decide you have enough resources to check each
PR/commit. It all depends on what HW you have available.
Description: OpenPGP digital signature