You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Alex Brett (JIRA)" <ji...@apache.org> on 2014/08/12 16:31:12 UTC

[jira] [Created] (CLOUDSTACK-7322) [Automation] Tag disruptive tests

Alex Brett created CLOUDSTACK-7322:
--------------------------------------

             Summary: [Automation] Tag disruptive tests
                 Key: CLOUDSTACK-7322
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7322
             Project: CloudStack
          Issue Type: Improvement
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Automation
            Reporter: Alex Brett
            Assignee: Alex Brett
             Fix For: 4.5.0


Some Marvin tests are disruptive, in that they cannot be run in parallel with other tests. An example being a test which reboots the secondary storage VM.

Current automation systems which run tests in parallel have manually defined lists of these disruptive tests - we should instead put an attribute on them, in order that they can be picked up by standard nosetests attribute filtering, and then run in serial.

I have a patch prepared which does this for known disruptive tests, and if accepted I will put some documentation on the wiki regarding how to identify tests which can't be run in parallel using nosetests.



--
This message was sent by Atlassian JIRA
(v6.2#6252)