tox -e dsvm-functional currently runs both functional and fullstack tests, because of this piece of code:
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/functional/__init__.py
This means that functional and fullstack tests can run in parallel in different workers. This is causing bad interaction as evident from this run:
http://logs.openstack.org/32/190832/6/check/check-neutron-dsvm-functional/b977f76/
I think that this sort of interaction is to be expected, and it's not worth trying to fix it. I think that fullstack tests should run in a separate job.
I'll change this in two patches:
1) Prepare for the fullstack CI job by running configure_host_for_func_testing for both functional and fullstack jobs, and stop messing around with test discovery during dsvm-functional: https://review.openstack.org/#/c/193905/
2) Send a patch to project-config to define the new job: https://review.openstack.org/#/c/193906/
Isn't this problem due to a failure in test isolation? Wouldn't it be preferable to solve that problem rather than requiring another testing node per patch?