-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15454/#review28792
-----------------------------------------------------------


Commit c2ea4fc3c7a880a2dedd9b21e7a8dca287557b39 in branch refs/heads/4.3 from 
Girish Shilamkar
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c2ea4fc ]

CLOUDSTACK-5147: Removing basic and sg tag from the test case which should not 
be run on basic zone setup

component.test_project_limits.TestMaxProjectNetworks.test_maxAccountNetworks 
tries to create multiple guest networks in an project of account which is not 
possible in basic zone as there is only one guest network allowed per zone in 
basic zone setup.
Hence removing the tags basic and sg so that this test case won't be picked up 
to run on basic zone setup.


- ASF Subversion and Git Services


On Nov. 12, 2013, 1:39 p.m., Gaurav Aradhye wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15454/
> -----------------------------------------------------------
> 
> (Updated Nov. 12, 2013, 1:39 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar and SrikanteswaraRao Talluri.
> 
> 
> Bugs: CLOUDSTACK-5147
>     https://issues.apache.org/jira/browse/CLOUDSTACK-5147
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> -------
> 
> component.test_project_limits.TestMaxProjectNetworks.test_maxAccountNetworks 
> tries to create multiple guest networks in an project of account which is not 
> possible in basic zone as there is only one guest network allowed per zone in 
> basic zone setup.
> 
> Hence removing the tags basic and sg so that this test case won't be picked 
> up to run on basic zone setup.
> 
> 
> Diffs
> -----
> 
>   test/integration/component/test_project_limits.py c6df7f3 
> 
> Diff: https://reviews.apache.org/r/15454/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Reply via email to