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


I think you should increase the number of expunge.workers in your deployment. 
The magic timeout here will again fail when the number of tests you are running 
in parallel increase exhausting the workers. Also we are already waiting for 2 
cycles of the expunge thread to ensure that we don't miss because of expunge 
thread exhaustion

- Prasanna Santhanam


On July 24, 2013, 12:02 a.m., Rayees Namathponnan wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12886/
> -----------------------------------------------------------
> 
> (Updated July 24, 2013, 12:02 a.m.)
> 
> 
> Review request for cloudstack, Alena Prokharchyk and Prasanna Santhanam.
> 
> 
> Bugs: CLOUDSTACK-2899
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> -------
> 
> Test case test_vm_life_cycle.py:test_09_expunge_vm failing during expunge;  
> if there are more than one expunge operation; expunge will be executed in 
> sequential;  in this we need to add some extra delay in test  apart from 
> expunage delay and expunge wait; add 60 sec in test case
> 
> 
> Diffs
> -----
> 
>   test/integration/smoke/test_vm_life_cycle.py c2c2592 
> 
> Diff: https://reviews.apache.org/r/12886/diff/
> 
> 
> Testing
> -------
> 
> Tested in KVM and VMware
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Reply via email to