Re: Storage functional tests CI job

Hi David, ----- Original Message ----- upstream. Currently the working job is vdsm_master_storage_functional_tests_localfs_gerrit, but we're working vdsm_master_storage_functional_tests_nfs_gerrit as well, and a new job Yoav requested based on vdsm_master_storage_functional_tests_localfs_gerrit . So instead all of the above and more we were thinking about a matrix job based on vdsm_master_storage_functional_tests_localfs_gerrit. We're only building vdsm. No, just building vdsm. It should run on every patchset, as does vdsm_master_storage_functional_tests_localfs_gerrit. Block, again as already configured in vdsm_master_storage_functional_tests_localfs_gerrit. build vdsm, some "cells" in the matrix should start services (rpcbind, nfs) we then stop at cleanup, some don't. Some might need network interfaces in the future, I'm not currently working on such a test. Right now - only stopping the above services, removing vdsm installation. The current job was configured based on some network job, since we didn't exactly what we should be doing, so I'm hopfull we don't still have garbage there. No. fedora 19/20, specifically 20. vdsm and supervdsm logs. already set to be cleaned at beginning and saved. currently we're running it based on env vars: sudo NOSE_WITH_XUNIT=1 \ VDSM_TEST_STORAGE_TYPES='localfs' \ VDSM_TEST_STORAGE_VERSIONS='0 3' \ ./run_tests.sh functional/storageTests.py All is basically already answered in the already existing job: vdsm_master_storage_functional_tests_nfs_gerrit . We need the matrix job to be based on this condiguration.