cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9453) Optimizing Marvin
Date Sun, 18 Sep 2016 14:00:25 GMT


ASF GitHub Bot commented on CLOUDSTACK-9453:

Github user jburwell commented on the issue:
    @abhinandanprateek ping regarding the Travis and Jenkins failures.  I would like to include
this PR in the upcoming,, and releases for which we plan to cut an
RC on 25 Sept 2016.

> Optimizing Marvin
> -----------------
>                 Key: CLOUDSTACK-9453
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: marvin
>    Affects Versions: Future
>            Reporter: Abhinandan Prateek
>            Assignee: Abhinandan Prateek
>             Fix For: Future
> Currently running all Marvin tests can take upto 4 days. The tests are not optimized
for nested cloud setup where most of the test automation runs. There are some simple things
that can be done to optimize the runs:
> 1. Have smaller default template: If we install macchinina template by default and use
it where there is no specific dependency on OS, then it will result in speeding up many of
Marvin tests.
> 2. Most of the tests have template names hard-coded. It will be a good idea to allow
some form of configuration so that test writers can use templates that better suit their test
> 3. Some test timeouts are unnecessary long and a failure can be deducted much early on
instead of undergoing several long timeouts.
> 4. Ability to tune service offerings to better suit marvin environments.

This message was sent by Atlassian JIRA

View raw message