RE: [Blocker] test duplicated in test_scale_vm.py

2015-09-30 Thread Somesh Naidu
Naidu Subject: Re: [Blocker] test duplicated in test_scale_vm.py @somesh, again your message is not helping all. > On Sep 30, 2015, at 5:09 PM, Somesh Naidu wrote: > >> that said we should still work towards a test set that can function as the > > So essentially, we are sayin

Re: [Blocker] test duplicated in test_scale_vm.py

2015-09-30 Thread Sebastien Goasguen
t;>>> Marvin Init Successful >>>>> ===final results are now copied to: >>>>> /tmp//MarvinLogs/test_scale_vm_OPS7AD=== >>>>> root@localhost:~/cloudstack# cd /tmp//MarvinLogs/test_scale_vm_OPS7AD >>>>> root@localhost:/tmp/MarvinLogs/

RE: [Blocker] test duplicated in test_scale_vm.py

2015-09-30 Thread Somesh Naidu
; You are right - only a subset of these tests are being run on "travis" > otherwise we will catch more or some of these failures. > > > > -Original Message- > > From: Sebastien Goasguen [mailto:run...@gmail.com] > > Sent: Wednesday, September 30, 2015 2

Re: [Blocker] test duplicated in test_scale_vm.py

2015-09-30 Thread Daan Hoogland
set of these tests are being run on "travis" > otherwise we will catch more or some of these failures. > > > > -Original Message- > > From: Sebastien Goasguen [mailto:run...@gmail.com] > > Sent: Wednesday, September 30, 2015 2:09 PM > > To: dev@cloudstack.apache.or

Re: [Blocker] test duplicated in test_scale_vm.py

2015-09-30 Thread Rajani Karuturi
tch more or some of these failures. > > -Original Message- > From: Sebastien Goasguen [mailto:run...@gmail.com] > Sent: Wednesday, September 30, 2015 2:09 PM > To: dev@cloudstack.apache.org > Subject: Re: [Blocker] test duplicated in test_scale_vm.py > > >> On

RE: [Blocker] test duplicated in test_scale_vm.py

2015-09-30 Thread Raja Pullela
" otherwise we will catch more or some of these failures. -Original Message- From: Sebastien Goasguen [mailto:run...@gmail.com] Sent: Wednesday, September 30, 2015 2:09 PM To: dev@cloudstack.apache.org Subject: Re: [Blocker] test duplicated in test_scale_vm.py > On Sep 30,

Re: [Blocker] test duplicated in test_scale_vm.py

2015-09-30 Thread Sebastien Goasguen
this failure correctly. > -Original Message- > From: Sebastien Goasguen [mailto:run...@gmail.com] > Sent: Wednesday, September 30, 2015 1:48 PM > To: dev@cloudstack.apache.org > Subject: Re: [Blocker] test duplicated in test_scale_vm.py > > >> On Sep 30,

RE: [Blocker] test duplicated in test_scale_vm.py

2015-09-30 Thread Raja Pullela
Yup... btw, I am on top of this and goal is to get to 100% passrate on BVTs! -Original Message- From: Sebastien Goasguen [mailto:run...@gmail.com] Sent: Wednesday, September 30, 2015 1:48 PM To: dev@cloudstack.apache.org Subject: Re: [Blocker] test duplicated in test_scale_vm.py >

Re: [Blocker] test duplicated in test_scale_vm.py

2015-09-30 Thread Sebastien Goasguen
p/MarvinLogs/test_scale_vm_OPS7AD# cat results.txt > Test scale virtual machine ... === TestName: test_01_scale_vm | Status : > SUCCESS === > ok > > -- > Ran 1 test in 23.455s > > OK > > -Original Message----- > From: Sebastien Goasguen [mailto:run...@gmail.com

RE: [Blocker] test duplicated in test_scale_vm.py

2015-09-30 Thread Raja Pullela
ESS === ok -- Ran 1 test in 23.455s OK -Original Message- From: Sebastien Goasguen [mailto:run...@gmail.com] Sent: Wednesday, September 30, 2015 1:04 PM To: dev@cloudstack.apache.org Subject: Re: [Blocker] test duplicated in test_scale_vm.py > On Sep 30, 2015, at 9:1

Re: [Blocker] test duplicated in test_scale_vm.py

2015-09-30 Thread Sebastien Goasguen
> On Sep 30, 2015, at 9:10 AM, Koushik Das wrote: > > Raja, > The earlier scale vm test couldn't run on simulator because of the validation > steps (IIRC it tries to connect to the real VM created during test). Since it > wasn't possible to run with simulator, the new test was added to run jus

RE: [Blocker] test duplicated in test_scale_vm.py

2015-09-30 Thread Koushik Das
Raja, The earlier scale vm test couldn't run on simulator because of the validation steps (IIRC it tries to connect to the real VM created during test). Since it wasn't possible to run with simulator, the new test was added to run just on the simulator. Check the required_hardware tag. -Ori