cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Animesh Chaturvedi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-7322) [Automation] Tag disruptive tests
Date Tue, 02 Dec 2014 19:37:21 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-7322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Animesh Chaturvedi updated CLOUDSTACK-7322:
-------------------------------------------

BULK EDIT> As you know 4.5 is getting ready for release and these New feature and Improvement
tickets are still open, please update the status. If the changes are not committed yet then
these tickets need to be moved out of 4.5

> [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.3.4#6332)

Mime
View raw message