Re: [Blocker] test duplicated in test_scale_vm.py

> 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

Re: [Blocker] test duplicated in test_scale_vm.py

st:/tmp/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 Goasgu

RE: [Blocker] test duplicated in test_scale_vm.py

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.

Re: [Blocker] test duplicated in test_scale_vm.py

ssment and Koushik report of 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 > >

RE: [Blocker] test duplicated in test_scale_vm.py

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

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

t - 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:09 PM > > To: dev@

RE: [Blocker] test duplicated in test_scale_vm.py

" 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

; > 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

RE: [Blocker] test duplicated in test_scale_vm.py

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 <somesh.na...@citrix.com> wrote: > >> that said we should still work towards a test set that can function as the >

Re: [Blocker] test duplicated in test_scale_vm.py

l.com] > Sent: Wednesday, September 30, 2015 5:44 AM > To: dev > Subject: Re: [Blocker] test duplicated in test_scale_vm.py > > I disagree, and let me carefully try to formulate why: BVT is useful and > 'should' be run before any thing is declared good. The problem is the >

RE: [Blocker] test duplicated in test_scale_vm.py

> > > 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