Re: marvin test cases + travis

[Abhinandan Prateek]

We can control the number of tests that travis runs. It is possible to say run 
more variety of test cases on each 10th run.
This will ensure that 9 out of 10 times travis runs a small sub set of tests. 
We can do this as travis provides the build number in an environment variable. 
If we can trigger the travis automatically at certain time of day then we can 
use that run to run just the regression suite. In that case we can have per 
commit run of smoke and once a day run of regression suite.

Even with this scheme we will need to increase the timeout. So I think it is ok 
to increase the timeout, but to get faster results most of the time, tune 
travis to run only a smaller subset of tests most of the time or for each 
commit.

If we leave out test cases out of travis that it can run, then we will be 
dependant on individuals/companies to do it once in a while and that is not 
automation.

With better control of travis we can have it run unit tests once (recently 
added by Rajani as an optimisation), have it run find bug, regressions say once 
in n runs etc. We should look forward to a highly customisable and useful 
travis instead of working in past limitations.


> On 02-May-2015, at 10:22 am, Raja Pullela  wrote:
>
> -1 for the time...
> since these tests run independently if we can spawn more threads/vms to bring 
> down the run time, that will be good.
> Another thing that can be looked at the run only tests in SMOKE folder.
> BTW, more tests in  "SMOKE"  should be added on a continuous basis.
>
> -Original Message-
> From: Rajani Karuturi [mailto:raj...@apache.org]
> Sent: Friday, May 1, 2015 11:09 PM
> To: dev@cloudstack.apache.org
> Subject: Re: marvin test cases + travis
>
> -1 on increasing the time
> As a reviewer, I would like an immediate response on a pull request. By the 
> time I review the code, if CI gives a +1(or -1) I can close the PR then and 
> there instead of coming back again to merge.
>
> I would suggest running all the jobs under 30 min and increasing the number 
> of parallel jobs as much as possible. we are running 10 jobs now. may be we 
> could increase this to 15(dont know if this is possible)
>
> we should aim to run only the smoke tests and not the entire regression suite 
> always.
>
> Making the jobs run on containers will speed them up. This needs some work on 
> removing the sudo dependency on the jobs (which is required to install some 
> additional packages and marvin).
>
> ~Rajani
>
> On Fri, May 1, 2015 at 8:25 AM, Abhinandan Prateek < 
> abhinandan.prat...@shapeblue.com> wrote:
>
>> +1 for increased timeouts.
>>
>> At the moment we get less than 24 commits per day on master. Only a
>> couple on other branches per day.
>> We can increase the timeout to upto 70 minutes or more. Will try to
>> ensure that in general a single run does not take more than an hour.
>>
>> A timeout window slightly higher will ensure that we do not see
>> timeout failures.
>>
>>> On 30-Apr-2015, at 11:25 pm, Daan Hoogland 
>> wrote:
>>>
>>> Travis is starting to indue the, 'oh,  a timeout again' - blindness
>>> in
>> me.
>>> Let's put a safe time on it.  A result should mean something and
>>> those
>> time
>>> out are like the (decreasing) abundance of Jenkins failures.
>>>
>>> So +1 for increasing the time
>>>
>>> On Thu, 30 Apr 2015 18:46 Ian Duffy  wrote:
>>>
>>>>> Do we need to ask for an increase in run time?
>>>>
>>>> From my experience I wouldn't say its required however *it would be
>>>> very nice*.
>>>> At the moment what we do is create new parallel jobs and balance
>>>> the tests across them so each job is under 50mins.
>>>>
>>>> Anywho, just my 2c, see what others say/think.
>>>>
>>>> On 30 April 2015 at 17:34, David Nalley  wrote:
>>>>> Do we need to ask for an increase in run time?
>>>>> 50 minutes is the OSS default, but the ASF is a paying customer
>>>>> and we can ask for longer timeouts.
>>>>>
>>>>> --David
>>>>>
>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek
>>>>>  wrote:
>>>>>> One of the run did timeout. Will balance the runs.
>>>>>>
>>>>>>> On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek <
>>>> abhinandan.prat...@shapeblue.com> wrote:
>>>>>>>
>>>>>>> Yes, thanks for checking. I was worried that now some of them
>>>>>>> may
>>>> start timin

Re: marvin test cases + travis

[Abhinandan Prateek]

I think it is a choice between fast response Vs more accurate response. I will 
rather wait for additional 20 minutes to get a better response.
With the commit rate we have that should not overload the system.
Yes we should definitely look for quality and coverage of the tests picked then 
the number.

> On 01-May-2015, at 11:09 pm, Rajani Karuturi  wrote:
>
> -1 on increasing the time
> As a reviewer, I would like an immediate response on a pull request. By the
> time I review the code, if CI gives a +1(or -1) I can close the PR then and
> there instead of coming back again to merge.
>
> I would suggest running all the jobs under 30 min and increasing the number
> of parallel jobs as much as possible. we are running 10 jobs now. may be we
> could increase this to 15(dont know if this is possible)
>
> we should aim to run only the smoke tests and not the entire regression
> suite always.
>
> Making the jobs run on containers will speed them up. This needs some work
> on removing the sudo dependency on the jobs (which is required to install
> some additional packages and marvin).
>
> ~Rajani
>
> On Fri, May 1, 2015 at 8:25 AM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>> +1 for increased timeouts.
>>
>> At the moment we get less than 24 commits per day on master. Only a couple
>> on other branches per day.
>> We can increase the timeout to upto 70 minutes or more. Will try to ensure
>> that in general a single run does not take more than an hour.
>>
>> A timeout window slightly higher will ensure that we do not see timeout
>> failures.
>>
>>> On 30-Apr-2015, at 11:25 pm, Daan Hoogland 
>> wrote:
>>>
>>> Travis is starting to indue the, 'oh,  a timeout again' - blindness in
>> me.
>>> Let's put a safe time on it.  A result should mean something and those
>> time
>>> out are like the (decreasing) abundance of Jenkins failures.
>>>
>>> So +1 for increasing the time
>>>
>>> On Thu, 30 Apr 2015 18:46 Ian Duffy  wrote:
>>>
> Do we need to ask for an increase in run time?

 From my experience I wouldn't say its required however *it would be very
 nice*.
 At the moment what we do is create new parallel jobs and balance the
 tests across them so each job is under 50mins.

 Anywho, just my 2c, see what others say/think.

 On 30 April 2015 at 17:34, David Nalley  wrote:
> Do we need to ask for an increase in run time?
> 50 minutes is the OSS default, but the ASF is a paying customer and we
> can ask for longer timeouts.
>
> --David
>
> On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek
>  wrote:
>> One of the run did timeout. Will balance the runs.
>>
>>> On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek <
 abhinandan.prat...@shapeblue.com> wrote:
>>>
>>> Yes, thanks for checking. I was worried that now some of them may
 start timing out.
>>> I have another 10 suites tested, will add them once everything seems
 fine.
>>>
>>> -abhi
>>>
>>>
 On 30-Apr-2015, at 5:32 pm, Rajani Karuturi 
 wrote:

 after correcting the test file path, its working fine

 https://travis-ci.org/karuturi/cloudstack/jobs/60681263



 ~Rajani

 On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi >>
 wrote:

> I think its due to this commit
>
>

>> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
>
> Here, test file name is changed from testname to
 [smoke,component]/testname
>
> But, while running each test file in the for loop, it prepends the
 name
> with smoke and hence, it cant find the file and none of the tests
>> in
 the
> file are run
>
>
>
> ~Rajani
>
> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>> It is possible, I will check.
>>
>>> On 30-Apr-2015, at 3:43 pm, Rajani Karuturi 
 wrote:
>>>
>>> Hey Abhi,
>>>
>>> In the recent travis runs, its not printing the test case in
 output (
>>> https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
>>>
>>> It used to print the test case name and status (
>>> https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
>>>
>>> Do you think it can be due to any recent changes?
>>>
>>> ~Rajani
>>>
>>> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
>>> abhinandan.prat...@shapeblue.com> wrote:
>>>

 There are more than 10 additional suites that can still be
 included
>> to
 the travis-CI.
 Since the current set runs comfortably I will go ahead and add
 more. If
 the system

Re: marvin test cases + travis

[Rohit Yadav]

Hi Rajani,

> On 01-May-2015, at 7:39 pm, Rajani Karuturi  wrote:
>
> -1 on increasing the time
> As a reviewer, I would like an immediate response on a pull request. By the
> time I review the code, if CI gives a +1(or -1) I can close the PR then and
> there instead of coming back again to merge.

I understand your sentiments but the issue was to increase the TravisCI job 
timeout. We can continue to optimize tests and build processes to decrease the 
round trip time.

> I would suggest running all the jobs under 30 min and increasing the number
> of parallel jobs as much as possible. we are running 10 jobs now. may be we
> could increase this to 15(dont know if this is possible)

A typical build on TravisCI is observed to take anywhere from 15-25 mins. That 
would only leave 5-15 mins for smoke tests to run, so we will have to aim to 
create jobs assuming the minimum available time window (5mins). Skipping unit 
tests could introduce regressions

> we should aim to run only the smoke tests and not the entire regression
> suite always.
>
> Making the jobs run on containers will speed them up. This needs some work
> on removing the sudo dependency on the jobs (which is required to install
> some additional packages and marvin).

Agree. But to do that we’ll have to figure out any other way to do the 
following;
- install, setup mysql-server, tomcat, uuid-runtime genisoimage 
python-setuptools python-pip
- pip installs
- install marvin

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

RE: marvin test cases + travis

[Raja Pullela]

-1 for the time... 
since these tests run independently if we can spawn more threads/vms to bring 
down the run time, that will be good.
Another thing that can be looked at the run only tests in SMOKE folder.   
BTW, more tests in  "SMOKE"  should be added on a continuous basis.

-Original Message-
From: Rajani Karuturi [mailto:raj...@apache.org] 
Sent: Friday, May 1, 2015 11:09 PM
To: dev@cloudstack.apache.org
Subject: Re: marvin test cases + travis

-1 on increasing the time
As a reviewer, I would like an immediate response on a pull request. By the 
time I review the code, if CI gives a +1(or -1) I can close the PR then and 
there instead of coming back again to merge.

I would suggest running all the jobs under 30 min and increasing the number of 
parallel jobs as much as possible. we are running 10 jobs now. may be we could 
increase this to 15(dont know if this is possible)

we should aim to run only the smoke tests and not the entire regression suite 
always.

Making the jobs run on containers will speed them up. This needs some work on 
removing the sudo dependency on the jobs (which is required to install some 
additional packages and marvin).

~Rajani

On Fri, May 1, 2015 at 8:25 AM, Abhinandan Prateek < 
abhinandan.prat...@shapeblue.com> wrote:

> +1 for increased timeouts.
>
> At the moment we get less than 24 commits per day on master. Only a 
> couple on other branches per day.
> We can increase the timeout to upto 70 minutes or more. Will try to 
> ensure that in general a single run does not take more than an hour.
>
> A timeout window slightly higher will ensure that we do not see 
> timeout failures.
>
> > On 30-Apr-2015, at 11:25 pm, Daan Hoogland 
> wrote:
> >
> > Travis is starting to indue the, 'oh,  a timeout again' - blindness 
> > in
> me.
> > Let's put a safe time on it.  A result should mean something and 
> > those
> time
> > out are like the (decreasing) abundance of Jenkins failures.
> >
> > So +1 for increasing the time
> >
> > On Thu, 30 Apr 2015 18:46 Ian Duffy  wrote:
> >
> >>> Do we need to ask for an increase in run time?
> >>
> >> From my experience I wouldn't say its required however *it would be 
> >> very nice*.
> >> At the moment what we do is create new parallel jobs and balance 
> >> the tests across them so each job is under 50mins.
> >>
> >> Anywho, just my 2c, see what others say/think.
> >>
> >> On 30 April 2015 at 17:34, David Nalley  wrote:
> >>> Do we need to ask for an increase in run time?
> >>> 50 minutes is the OSS default, but the ASF is a paying customer 
> >>> and we can ask for longer timeouts.
> >>>
> >>> --David
> >>>
> >>> On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek 
> >>>  wrote:
> >>>> One of the run did timeout. Will balance the runs.
> >>>>
> >>>>> On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek <
> >> abhinandan.prat...@shapeblue.com> wrote:
> >>>>>
> >>>>> Yes, thanks for checking. I was worried that now some of them 
> >>>>> may
> >> start timing out.
> >>>>> I have another 10 suites tested, will add them once everything 
> >>>>> seems
> >> fine.
> >>>>>
> >>>>> -abhi
> >>>>>
> >>>>>
> >>>>>> On 30-Apr-2015, at 5:32 pm, Rajani Karuturi 
> >> wrote:
> >>>>>>
> >>>>>> after correcting the test file path, its working fine
> >>>>>>
> >>>>>> https://travis-ci.org/karuturi/cloudstack/jobs/60681263
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> ~Rajani
> >>>>>>
> >>>>>> On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi 
> >>>>>>  >
> >> wrote:
> >>>>>>
> >>>>>>> I think its due to this commit
> >>>>>>>
> >>>>>>>
> >>
> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126
> b96cf9b3fbee77
> >>>>>>>
> >>>>>>> Here, test file name is changed from testname to
> >> [smoke,component]/testname
> >>>>>>>
> >>>>>>> But, while running each test file in the for loop, it prepends 
> >>>>>>> the
> >> name
> >>>>>>> with smoke 

Re: marvin test cases + travis

[Daan Hoogland]

If we can lets increase, but if we can't let's not allow for false negatives

Op vr 1 mei 2015 om 19:39 schreef Rajani Karuturi :

> -1 on increasing the time
> As a reviewer, I would like an immediate response on a pull request. By the
> time I review the code, if CI gives a +1(or -1) I can close the PR then and
> there instead of coming back again to merge.
>
> I would suggest running all the jobs under 30 min and increasing the number
> of parallel jobs as much as possible. we are running 10 jobs now. may be we
> could increase this to 15(dont know if this is possible)
>
> we should aim to run only the smoke tests and not the entire regression
> suite always.
>
> Making the jobs run on containers will speed them up. This needs some work
> on removing the sudo dependency on the jobs (which is required to install
> some additional packages and marvin).
>
> ~Rajani
>
> On Fri, May 1, 2015 at 8:25 AM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
> > +1 for increased timeouts.
> >
> > At the moment we get less than 24 commits per day on master. Only a
> couple
> > on other branches per day.
> > We can increase the timeout to upto 70 minutes or more. Will try to
> ensure
> > that in general a single run does not take more than an hour.
> >
> > A timeout window slightly higher will ensure that we do not see timeout
> > failures.
> >
> > > On 30-Apr-2015, at 11:25 pm, Daan Hoogland 
> > wrote:
> > >
> > > Travis is starting to indue the, 'oh,  a timeout again' - blindness in
> > me.
> > > Let's put a safe time on it.  A result should mean something and those
> > time
> > > out are like the (decreasing) abundance of Jenkins failures.
> > >
> > > So +1 for increasing the time
> > >
> > > On Thu, 30 Apr 2015 18:46 Ian Duffy  wrote:
> > >
> > >>> Do we need to ask for an increase in run time?
> > >>
> > >> From my experience I wouldn't say its required however *it would be
> very
> > >> nice*.
> > >> At the moment what we do is create new parallel jobs and balance the
> > >> tests across them so each job is under 50mins.
> > >>
> > >> Anywho, just my 2c, see what others say/think.
> > >>
> > >> On 30 April 2015 at 17:34, David Nalley  wrote:
> > >>> Do we need to ask for an increase in run time?
> > >>> 50 minutes is the OSS default, but the ASF is a paying customer and
> we
> > >>> can ask for longer timeouts.
> > >>>
> > >>> --David
> > >>>
> > >>> On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek
> > >>>  wrote:
> >  One of the run did timeout. Will balance the runs.
> > 
> > > On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek <
> > >> abhinandan.prat...@shapeblue.com> wrote:
> > >
> > > Yes, thanks for checking. I was worried that now some of them may
> > >> start timing out.
> > > I have another 10 suites tested, will add them once everything
> seems
> > >> fine.
> > >
> > > -abhi
> > >
> > >
> > >> On 30-Apr-2015, at 5:32 pm, Rajani Karuturi 
> > >> wrote:
> > >>
> > >> after correcting the test file path, its working fine
> > >>
> > >> https://travis-ci.org/karuturi/cloudstack/jobs/60681263
> > >>
> > >>
> > >>
> > >> ~Rajani
> > >>
> > >> On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi <
> raj...@apache.org
> > >
> > >> wrote:
> > >>
> > >>> I think its due to this commit
> > >>>
> > >>>
> > >>
> >
> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
> > >>>
> > >>> Here, test file name is changed from testname to
> > >> [smoke,component]/testname
> > >>>
> > >>> But, while running each test file in the for loop, it prepends
> the
> > >> name
> > >>> with smoke and hence, it cant find the file and none of the tests
> > in
> > >> the
> > >>> file are run
> > >>>
> > >>>
> > >>>
> > >>> ~Rajani
> > >>>
> > >>> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
> > >>> abhinandan.prat...@shapeblue.com> wrote:
> > >>>
> >  It is possible, I will check.
> > 
> > > On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  >
> > >> wrote:
> > >
> > > Hey Abhi,
> > >
> > > In the recent travis runs, its not printing the test case in
> > >> output (
> > > https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
> > >
> > > It used to print the test case name and status (
> > > https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
> > >
> > > Do you think it can be due to any recent changes?
> > >
> > > ~Rajani
> > >
> > > On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> > > abhinandan.prat...@shapeblue.com> wrote:
> > >
> > >>
> > >> There are more than 10 additional suites that can still be
> > >> included
> >  to
> > >> the travis-CI.
> > >> Since the current set runs comfortably I will go ahead and add
> > >

Re: marvin test cases + travis

[Rajani Karuturi]

-1 on increasing the time
As a reviewer, I would like an immediate response on a pull request. By the
time I review the code, if CI gives a +1(or -1) I can close the PR then and
there instead of coming back again to merge.

I would suggest running all the jobs under 30 min and increasing the number
of parallel jobs as much as possible. we are running 10 jobs now. may be we
could increase this to 15(dont know if this is possible)

we should aim to run only the smoke tests and not the entire regression
suite always.

Making the jobs run on containers will speed them up. This needs some work
on removing the sudo dependency on the jobs (which is required to install
some additional packages and marvin).

~Rajani

On Fri, May 1, 2015 at 8:25 AM, Abhinandan Prateek <
abhinandan.prat...@shapeblue.com> wrote:

> +1 for increased timeouts.
>
> At the moment we get less than 24 commits per day on master. Only a couple
> on other branches per day.
> We can increase the timeout to upto 70 minutes or more. Will try to ensure
> that in general a single run does not take more than an hour.
>
> A timeout window slightly higher will ensure that we do not see timeout
> failures.
>
> > On 30-Apr-2015, at 11:25 pm, Daan Hoogland 
> wrote:
> >
> > Travis is starting to indue the, 'oh,  a timeout again' - blindness in
> me.
> > Let's put a safe time on it.  A result should mean something and those
> time
> > out are like the (decreasing) abundance of Jenkins failures.
> >
> > So +1 for increasing the time
> >
> > On Thu, 30 Apr 2015 18:46 Ian Duffy  wrote:
> >
> >>> Do we need to ask for an increase in run time?
> >>
> >> From my experience I wouldn't say its required however *it would be very
> >> nice*.
> >> At the moment what we do is create new parallel jobs and balance the
> >> tests across them so each job is under 50mins.
> >>
> >> Anywho, just my 2c, see what others say/think.
> >>
> >> On 30 April 2015 at 17:34, David Nalley  wrote:
> >>> Do we need to ask for an increase in run time?
> >>> 50 minutes is the OSS default, but the ASF is a paying customer and we
> >>> can ask for longer timeouts.
> >>>
> >>> --David
> >>>
> >>> On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek
> >>>  wrote:
>  One of the run did timeout. Will balance the runs.
> 
> > On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek <
> >> abhinandan.prat...@shapeblue.com> wrote:
> >
> > Yes, thanks for checking. I was worried that now some of them may
> >> start timing out.
> > I have another 10 suites tested, will add them once everything seems
> >> fine.
> >
> > -abhi
> >
> >
> >> On 30-Apr-2015, at 5:32 pm, Rajani Karuturi 
> >> wrote:
> >>
> >> after correcting the test file path, its working fine
> >>
> >> https://travis-ci.org/karuturi/cloudstack/jobs/60681263
> >>
> >>
> >>
> >> ~Rajani
> >>
> >> On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi  >
> >> wrote:
> >>
> >>> I think its due to this commit
> >>>
> >>>
> >>
> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
> >>>
> >>> Here, test file name is changed from testname to
> >> [smoke,component]/testname
> >>>
> >>> But, while running each test file in the for loop, it prepends the
> >> name
> >>> with smoke and hence, it cant find the file and none of the tests
> in
> >> the
> >>> file are run
> >>>
> >>>
> >>>
> >>> ~Rajani
> >>>
> >>> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
> >>> abhinandan.prat...@shapeblue.com> wrote:
> >>>
>  It is possible, I will check.
> 
> > On 30-Apr-2015, at 3:43 pm, Rajani Karuturi 
> >> wrote:
> >
> > Hey Abhi,
> >
> > In the recent travis runs, its not printing the test case in
> >> output (
> > https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
> >
> > It used to print the test case name and status (
> > https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
> >
> > Do you think it can be due to any recent changes?
> >
> > ~Rajani
> >
> > On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> > abhinandan.prat...@shapeblue.com> wrote:
> >
> >>
> >> There are more than 10 additional suites that can still be
> >> included
>  to
> >> the travis-CI.
> >> Since the current set runs comfortably I will go ahead and add
> >> more. If
> >> the system gets overloaded, then we can balance the kind of test
>  suites and
> >> amount of test suits that run comfortably on travis.
> >>
> >> -abhi
> >>
> >>
> >>
> >>
> >> Find out more about ShapeBlue and our range of CloudStack
> related
>  services
> >>
> >> IaaS Cloud Design & Build<
> >> http://shapeblue.c

Re: marvin test cases + travis

[Rajani Karuturi]

At the moment we are creating 10 parallel jobs and in each job we do
1. mvn clean install
2. deploydb, deploy datacenter
3. run tests

if we change step 1 to mvn clean install -DskipTests=true and run junit
tests only in one job, that would save time.

Also, with earlier 5 jobs setup, it used to run fine on my private fork.
Now, it takes double the time(as it runs only 5 parallel jobs) and usually
timesout




~Rajani

On Fri, May 1, 2015 at 8:25 AM, Abhinandan Prateek <
abhinandan.prat...@shapeblue.com> wrote:

> +1 for increased timeouts.
>
> At the moment we get less than 24 commits per day on master. Only a couple
> on other branches per day.
> We can increase the timeout to upto 70 minutes or more. Will try to ensure
> that in general a single run does not take more than an hour.
>
> A timeout window slightly higher will ensure that we do not see timeout
> failures.
>
> > On 30-Apr-2015, at 11:25 pm, Daan Hoogland 
> wrote:
> >
> > Travis is starting to indue the, 'oh,  a timeout again' - blindness in
> me.
> > Let's put a safe time on it.  A result should mean something and those
> time
> > out are like the (decreasing) abundance of Jenkins failures.
> >
> > So +1 for increasing the time
> >
> > On Thu, 30 Apr 2015 18:46 Ian Duffy  wrote:
> >
> >>> Do we need to ask for an increase in run time?
> >>
> >> From my experience I wouldn't say its required however *it would be very
> >> nice*.
> >> At the moment what we do is create new parallel jobs and balance the
> >> tests across them so each job is under 50mins.
> >>
> >> Anywho, just my 2c, see what others say/think.
> >>
> >> On 30 April 2015 at 17:34, David Nalley  wrote:
> >>> Do we need to ask for an increase in run time?
> >>> 50 minutes is the OSS default, but the ASF is a paying customer and we
> >>> can ask for longer timeouts.
> >>>
> >>> --David
> >>>
> >>> On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek
> >>>  wrote:
>  One of the run did timeout. Will balance the runs.
> 
> > On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek <
> >> abhinandan.prat...@shapeblue.com> wrote:
> >
> > Yes, thanks for checking. I was worried that now some of them may
> >> start timing out.
> > I have another 10 suites tested, will add them once everything seems
> >> fine.
> >
> > -abhi
> >
> >
> >> On 30-Apr-2015, at 5:32 pm, Rajani Karuturi 
> >> wrote:
> >>
> >> after correcting the test file path, its working fine
> >>
> >> https://travis-ci.org/karuturi/cloudstack/jobs/60681263
> >>
> >>
> >>
> >> ~Rajani
> >>
> >> On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi  >
> >> wrote:
> >>
> >>> I think its due to this commit
> >>>
> >>>
> >>
> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
> >>>
> >>> Here, test file name is changed from testname to
> >> [smoke,component]/testname
> >>>
> >>> But, while running each test file in the for loop, it prepends the
> >> name
> >>> with smoke and hence, it cant find the file and none of the tests
> in
> >> the
> >>> file are run
> >>>
> >>>
> >>>
> >>> ~Rajani
> >>>
> >>> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
> >>> abhinandan.prat...@shapeblue.com> wrote:
> >>>
>  It is possible, I will check.
> 
> > On 30-Apr-2015, at 3:43 pm, Rajani Karuturi 
> >> wrote:
> >
> > Hey Abhi,
> >
> > In the recent travis runs, its not printing the test case in
> >> output (
> > https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
> >
> > It used to print the test case name and status (
> > https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
> >
> > Do you think it can be due to any recent changes?
> >
> > ~Rajani
> >
> > On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> > abhinandan.prat...@shapeblue.com> wrote:
> >
> >>
> >> There are more than 10 additional suites that can still be
> >> included
>  to
> >> the travis-CI.
> >> Since the current set runs comfortably I will go ahead and add
> >> more. If
> >> the system gets overloaded, then we can balance the kind of test
>  suites and
> >> amount of test suits that run comfortably on travis.
> >>
> >> -abhi
> >>
> >>
> >>
> >>
> >> Find out more about ShapeBlue and our range of CloudStack
> related
>  services
> >>
> >> IaaS Cloud Design & Build<
> >> http://shapeblue.com/iaas-cloud-design-and-build//>
> >> CSForge – rapid IaaS deployment framework<
>  http://shapeblue.com/csforge/>
> >> CloudStack Consulting<
> >> http://shapeblue.com/cloudstack-consultancy/>
> >> CloudStack Software Engineering<
> >> http://shapeblue.

Re: marvin test cases + travis

[Abhinandan Prateek]

+1 for increased timeouts.

At the moment we get less than 24 commits per day on master. Only a couple on 
other branches per day.
We can increase the timeout to upto 70 minutes or more. Will try to ensure that 
in general a single run does not take more than an hour.

A timeout window slightly higher will ensure that we do not see timeout 
failures.

> On 30-Apr-2015, at 11:25 pm, Daan Hoogland  wrote:
>
> Travis is starting to indue the, 'oh,  a timeout again' - blindness in me.
> Let's put a safe time on it.  A result should mean something and those time
> out are like the (decreasing) abundance of Jenkins failures.
>
> So +1 for increasing the time
>
> On Thu, 30 Apr 2015 18:46 Ian Duffy  wrote:
>
>>> Do we need to ask for an increase in run time?
>>
>> From my experience I wouldn't say its required however *it would be very
>> nice*.
>> At the moment what we do is create new parallel jobs and balance the
>> tests across them so each job is under 50mins.
>>
>> Anywho, just my 2c, see what others say/think.
>>
>> On 30 April 2015 at 17:34, David Nalley  wrote:
>>> Do we need to ask for an increase in run time?
>>> 50 minutes is the OSS default, but the ASF is a paying customer and we
>>> can ask for longer timeouts.
>>>
>>> --David
>>>
>>> On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek
>>>  wrote:
 One of the run did timeout. Will balance the runs.

> On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek <
>> abhinandan.prat...@shapeblue.com> wrote:
>
> Yes, thanks for checking. I was worried that now some of them may
>> start timing out.
> I have another 10 suites tested, will add them once everything seems
>> fine.
>
> -abhi
>
>
>> On 30-Apr-2015, at 5:32 pm, Rajani Karuturi 
>> wrote:
>>
>> after correcting the test file path, its working fine
>>
>> https://travis-ci.org/karuturi/cloudstack/jobs/60681263
>>
>>
>>
>> ~Rajani
>>
>> On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi 
>> wrote:
>>
>>> I think its due to this commit
>>>
>>>
>> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
>>>
>>> Here, test file name is changed from testname to
>> [smoke,component]/testname
>>>
>>> But, while running each test file in the for loop, it prepends the
>> name
>>> with smoke and hence, it cant find the file and none of the tests in
>> the
>>> file are run
>>>
>>>
>>>
>>> ~Rajani
>>>
>>> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
>>> abhinandan.prat...@shapeblue.com> wrote:
>>>
 It is possible, I will check.

> On 30-Apr-2015, at 3:43 pm, Rajani Karuturi 
>> wrote:
>
> Hey Abhi,
>
> In the recent travis runs, its not printing the test case in
>> output (
> https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
>
> It used to print the test case name and status (
> https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
>
> Do you think it can be due to any recent changes?
>
> ~Rajani
>
> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>>
>> There are more than 10 additional suites that can still be
>> included
 to
>> the travis-CI.
>> Since the current set runs comfortably I will go ahead and add
>> more. If
>> the system gets overloaded, then we can balance the kind of test
 suites and
>> amount of test suits that run comfortably on travis.
>>
>> -abhi
>>
>>
>>
>>
>> Find out more about ShapeBlue and our range of CloudStack related
 services
>>
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework<
 http://shapeblue.com/csforge/>
>> CloudStack Consulting<
>> http://shapeblue.com/cloudstack-consultancy/>
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>>
>> This email and any attachments to it may be confidential and are
 intended
>> solely for the use of the individual to whom it is addressed. Any
 views or
>> opinions expressed are solely those of the author and do not
 necessarily
>> represent those of Shape Blue Ltd or related companies. If you
>> are not
 the
>> intended recipient of this email, you must neither take any action
 based
>> upon its contents, nor copy or show it to an

Re: marvin test cases + travis

[Daan Hoogland]

Travis is starting to indue the, 'oh,  a timeout again' - blindness in me.
Let's put a safe time on it.  A result should mean something and those time
out are like the (decreasing) abundance of Jenkins failures.

So +1 for increasing the time

On Thu, 30 Apr 2015 18:46 Ian Duffy  wrote:

> > Do we need to ask for an increase in run time?
>
> From my experience I wouldn't say its required however *it would be very
> nice*.
> At the moment what we do is create new parallel jobs and balance the
> tests across them so each job is under 50mins.
>
> Anywho, just my 2c, see what others say/think.
>
> On 30 April 2015 at 17:34, David Nalley  wrote:
> > Do we need to ask for an increase in run time?
> > 50 minutes is the OSS default, but the ASF is a paying customer and we
> > can ask for longer timeouts.
> >
> > --David
> >
> > On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek
> >  wrote:
> >> One of the run did timeout. Will balance the runs.
> >>
> >>> On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
> >>>
> >>> Yes, thanks for checking. I was worried that now some of them may
> start timing out.
> >>> I have another 10 suites tested, will add them once everything seems
> fine.
> >>>
> >>> -abhi
> >>>
> >>>
>  On 30-Apr-2015, at 5:32 pm, Rajani Karuturi 
> wrote:
> 
>  after correcting the test file path, its working fine
> 
>  https://travis-ci.org/karuturi/cloudstack/jobs/60681263
> 
> 
> 
>  ~Rajani
> 
>  On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi 
> wrote:
> 
> > I think its due to this commit
> >
> >
> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
> >
> > Here, test file name is changed from testname to
> [smoke,component]/testname
> >
> > But, while running each test file in the for loop, it prepends the
> name
> > with smoke and hence, it cant find the file and none of the tests in
> the
> > file are run
> >
> >
> >
> > ~Rajani
> >
> > On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
> > abhinandan.prat...@shapeblue.com> wrote:
> >
> >> It is possible, I will check.
> >>
> >>> On 30-Apr-2015, at 3:43 pm, Rajani Karuturi 
> wrote:
> >>>
> >>> Hey Abhi,
> >>>
> >>> In the recent travis runs, its not printing the test case in
> output (
> >>> https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
> >>>
> >>> It used to print the test case name and status (
> >>> https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
> >>>
> >>> Do you think it can be due to any recent changes?
> >>>
> >>> ~Rajani
> >>>
> >>> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> >>> abhinandan.prat...@shapeblue.com> wrote:
> >>>
> 
>   There are more than 10 additional suites that can still be
> included
> >> to
>  the travis-CI.
>  Since the current set runs comfortably I will go ahead and add
> more. If
>  the system gets overloaded, then we can balance the kind of test
> >> suites and
>  amount of test suits that run comfortably on travis.
> 
>  -abhi
> 
> 
> 
> 
>  Find out more about ShapeBlue and our range of CloudStack related
> >> services
> 
>  IaaS Cloud Design & Build<
>  http://shapeblue.com/iaas-cloud-design-and-build//>
>  CSForge – rapid IaaS deployment framework<
> >> http://shapeblue.com/csforge/>
>  CloudStack Consulting<
> http://shapeblue.com/cloudstack-consultancy/>
>  CloudStack Software Engineering<
>  http://shapeblue.com/cloudstack-software-engineering/>
>  CloudStack Infrastructure Support<
>  http://shapeblue.com/cloudstack-infrastructure-support/>
>  CloudStack Bootcamp Training Courses<
>  http://shapeblue.com/cloudstack-training/>
> 
>  This email and any attachments to it may be confidential and are
> >> intended
>  solely for the use of the individual to whom it is addressed. Any
> >> views or
>  opinions expressed are solely those of the author and do not
> >> necessarily
>  represent those of Shape Blue Ltd or related companies. If you
> are not
> >> the
>  intended recipient of this email, you must neither take any action
> >> based
>  upon its contents, nor copy or show it to anyone. Please contact
> the
> >> sender
>  if you believe you have received this email in error. Shape Blue
> Ltd
> >> is a
>  company incorporated in England & Wales. ShapeBlue Services India
> LLP
> >> is a
>  company incorporated in India and is operated under license from
> Shape
> >> Blue
>  Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated
> in
> >> Brasil
>  an

Re: marvin test cases + travis

[Ian Duffy]

> Do we need to ask for an increase in run time?

>From my experience I wouldn't say its required however *it would be very nice*.
At the moment what we do is create new parallel jobs and balance the
tests across them so each job is under 50mins.

Anywho, just my 2c, see what others say/think.

On 30 April 2015 at 17:34, David Nalley  wrote:
> Do we need to ask for an increase in run time?
> 50 minutes is the OSS default, but the ASF is a paying customer and we
> can ask for longer timeouts.
>
> --David
>
> On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek
>  wrote:
>> One of the run did timeout. Will balance the runs.
>>
>>> On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek 
>>>  wrote:
>>>
>>> Yes, thanks for checking. I was worried that now some of them may start 
>>> timing out.
>>> I have another 10 suites tested, will add them once everything seems fine.
>>>
>>> -abhi
>>>
>>>
 On 30-Apr-2015, at 5:32 pm, Rajani Karuturi  wrote:

 after correcting the test file path, its working fine

 https://travis-ci.org/karuturi/cloudstack/jobs/60681263



 ~Rajani

 On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi  wrote:

> I think its due to this commit
>
> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
>
> Here, test file name is changed from testname to 
> [smoke,component]/testname
>
> But, while running each test file in the for loop, it prepends the name
> with smoke and hence, it cant find the file and none of the tests in the
> file are run
>
>
>
> ~Rajani
>
> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>> It is possible, I will check.
>>
>>> On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  wrote:
>>>
>>> Hey Abhi,
>>>
>>> In the recent travis runs, its not printing the test case in output (
>>> https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
>>>
>>> It used to print the test case name and status (
>>> https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
>>>
>>> Do you think it can be due to any recent changes?
>>>
>>> ~Rajani
>>>
>>> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
>>> abhinandan.prat...@shapeblue.com> wrote:
>>>

  There are more than 10 additional suites that can still be included
>> to
 the travis-CI.
 Since the current set runs comfortably I will go ahead and add more. If
 the system gets overloaded, then we can balance the kind of test
>> suites and
 amount of test suits that run comfortably on travis.

 -abhi




 Find out more about ShapeBlue and our range of CloudStack related
>> services

 IaaS Cloud Design & Build<
 http://shapeblue.com/iaas-cloud-design-and-build//>
 CSForge – rapid IaaS deployment framework<
>> http://shapeblue.com/csforge/>
 CloudStack Consulting
 CloudStack Software Engineering<
 http://shapeblue.com/cloudstack-software-engineering/>
 CloudStack Infrastructure Support<
 http://shapeblue.com/cloudstack-infrastructure-support/>
 CloudStack Bootcamp Training Courses<
 http://shapeblue.com/cloudstack-training/>

 This email and any attachments to it may be confidential and are
>> intended
 solely for the use of the individual to whom it is addressed. Any
>> views or
 opinions expressed are solely those of the author and do not
>> necessarily
 represent those of Shape Blue Ltd or related companies. If you are not
>> the
 intended recipient of this email, you must neither take any action
>> based
 upon its contents, nor copy or show it to anyone. Please contact the
>> sender
 if you believe you have received this email in error. Shape Blue Ltd
>> is a
 company incorporated in England & Wales. ShapeBlue Services India LLP
>> is a
 company incorporated in India and is operated under license from Shape
>> Blue
 Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
>> Brasil
 and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty
>> Ltd is
 a company registered by The Republic of South Africa and is traded
>> under
 license from Shape Blue Ltd. ShapeBlue is a registered trademark.

>>
>> Find out more about ShapeBlue and our range of CloudStack related 
>> services
>>
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting

Re: marvin test cases + travis

[David Nalley]

Do we need to ask for an increase in run time?
50 minutes is the OSS default, but the ASF is a paying customer and we
can ask for longer timeouts.

--David

On Thu, Apr 30, 2015 at 10:06 AM, Abhinandan Prateek
 wrote:
> One of the run did timeout. Will balance the runs.
>
>> On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek 
>>  wrote:
>>
>> Yes, thanks for checking. I was worried that now some of them may start 
>> timing out.
>> I have another 10 suites tested, will add them once everything seems fine.
>>
>> -abhi
>>
>>
>>> On 30-Apr-2015, at 5:32 pm, Rajani Karuturi  wrote:
>>>
>>> after correcting the test file path, its working fine
>>>
>>> https://travis-ci.org/karuturi/cloudstack/jobs/60681263
>>>
>>>
>>>
>>> ~Rajani
>>>
>>> On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi  wrote:
>>>
 I think its due to this commit

 https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77

 Here, test file name is changed from testname to [smoke,component]/testname

 But, while running each test file in the for loop, it prepends the name
 with smoke and hence, it cant find the file and none of the tests in the
 file are run



 ~Rajani

 On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
 abhinandan.prat...@shapeblue.com> wrote:

> It is possible, I will check.
>
>> On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  wrote:
>>
>> Hey Abhi,
>>
>> In the recent travis runs, its not printing the test case in output (
>> https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
>>
>> It used to print the test case name and status (
>> https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
>>
>> Do you think it can be due to any recent changes?
>>
>> ~Rajani
>>
>> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
>> abhinandan.prat...@shapeblue.com> wrote:
>>
>>>
>>>  There are more than 10 additional suites that can still be included
> to
>>> the travis-CI.
>>> Since the current set runs comfortably I will go ahead and add more. If
>>> the system gets overloaded, then we can balance the kind of test
> suites and
>>> amount of test suits that run comfortably on travis.
>>>
>>> -abhi
>>>
>>>
>>>
>>>
>>> Find out more about ShapeBlue and our range of CloudStack related
> services
>>>
>>> IaaS Cloud Design & Build<
>>> http://shapeblue.com/iaas-cloud-design-and-build//>
>>> CSForge – rapid IaaS deployment framework<
> http://shapeblue.com/csforge/>
>>> CloudStack Consulting
>>> CloudStack Software Engineering<
>>> http://shapeblue.com/cloudstack-software-engineering/>
>>> CloudStack Infrastructure Support<
>>> http://shapeblue.com/cloudstack-infrastructure-support/>
>>> CloudStack Bootcamp Training Courses<
>>> http://shapeblue.com/cloudstack-training/>
>>>
>>> This email and any attachments to it may be confidential and are
> intended
>>> solely for the use of the individual to whom it is addressed. Any
> views or
>>> opinions expressed are solely those of the author and do not
> necessarily
>>> represent those of Shape Blue Ltd or related companies. If you are not
> the
>>> intended recipient of this email, you must neither take any action
> based
>>> upon its contents, nor copy or show it to anyone. Please contact the
> sender
>>> if you believe you have received this email in error. Shape Blue Ltd
> is a
>>> company incorporated in England & Wales. ShapeBlue Services India LLP
> is a
>>> company incorporated in India and is operated under license from Shape
> Blue
>>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
> Brasil
>>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty
> Ltd is
>>> a company registered by The Republic of South Africa and is traded
> under
>>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>>
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering<
> http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions express

Re: marvin test cases + travis

[Abhinandan Prateek]

One of the run did timeout. Will balance the runs.

> On 30-Apr-2015, at 5:59 pm, Abhinandan Prateek 
>  wrote:
>
> Yes, thanks for checking. I was worried that now some of them may start 
> timing out.
> I have another 10 suites tested, will add them once everything seems fine.
>
> -abhi
>
>
>> On 30-Apr-2015, at 5:32 pm, Rajani Karuturi  wrote:
>>
>> after correcting the test file path, its working fine
>>
>> https://travis-ci.org/karuturi/cloudstack/jobs/60681263
>>
>>
>>
>> ~Rajani
>>
>> On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi  wrote:
>>
>>> I think its due to this commit
>>>
>>> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
>>>
>>> Here, test file name is changed from testname to [smoke,component]/testname
>>>
>>> But, while running each test file in the for loop, it prepends the name
>>> with smoke and hence, it cant find the file and none of the tests in the
>>> file are run
>>>
>>>
>>>
>>> ~Rajani
>>>
>>> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
>>> abhinandan.prat...@shapeblue.com> wrote:
>>>
 It is possible, I will check.

> On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  wrote:
>
> Hey Abhi,
>
> In the recent travis runs, its not printing the test case in output (
> https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
>
> It used to print the test case name and status (
> https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
>
> Do you think it can be due to any recent changes?
>
> ~Rajani
>
> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>>
>>  There are more than 10 additional suites that can still be included
 to
>> the travis-CI.
>> Since the current set runs comfortably I will go ahead and add more. If
>> the system gets overloaded, then we can balance the kind of test
 suites and
>> amount of test suits that run comfortably on travis.
>>
>> -abhi
>>
>>
>>
>>
>> Find out more about ShapeBlue and our range of CloudStack related
 services
>>
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework<
 http://shapeblue.com/csforge/>
>> CloudStack Consulting
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>>
>> This email and any attachments to it may be confidential and are
 intended
>> solely for the use of the individual to whom it is addressed. Any
 views or
>> opinions expressed are solely those of the author and do not
 necessarily
>> represent those of Shape Blue Ltd or related companies. If you are not
 the
>> intended recipient of this email, you must neither take any action
 based
>> upon its contents, nor copy or show it to anyone. Please contact the
 sender
>> if you believe you have received this email in error. Shape Blue Ltd
 is a
>> company incorporated in England & Wales. ShapeBlue Services India LLP
 is a
>> company incorporated in India and is operated under license from Shape
 Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
 Brasil
>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty
 Ltd is
>> a company registered by The Republic of South Africa and is traded
 under
>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>

 Find out more about ShapeBlue and our range of CloudStack related services

 IaaS Cloud Design & Build<
 http://shapeblue.com/iaas-cloud-design-and-build//>
 CSForge – rapid IaaS deployment framework
 CloudStack Consulting
 CloudStack Software Engineering<
 http://shapeblue.com/cloudstack-software-engineering/>
 CloudStack Infrastructure Support<
 http://shapeblue.com/cloudstack-infrastructure-support/>
 CloudStack Bootcamp Training Courses<
 http://shapeblue.com/cloudstack-training/>

 This email and any attachments to it may be confidential and are intended
 solely for the use of the individual to whom it is addressed. Any views or
 opinions expressed are solely those of the author and do not necessarily
 represent those of Shape Blue Ltd or related companies. If you are not the
 intended recipient of this email, you must neither take any action based
 upon its contents, nor copy or show it to anyone. Please contact the sender
 if you believe you have received this email in err

Re: marvin test cases + travis

[Abhinandan Prateek]

Yes, thanks for checking. I was worried that now some of them may start timing 
out.
I have another 10 suites tested, will add them once everything seems fine.

-abhi


> On 30-Apr-2015, at 5:32 pm, Rajani Karuturi  wrote:
>
> after correcting the test file path, its working fine
>
> https://travis-ci.org/karuturi/cloudstack/jobs/60681263
>
>
>
> ~Rajani
>
> On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi  wrote:
>
>> I think its due to this commit
>>
>> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
>>
>> Here, test file name is changed from testname to [smoke,component]/testname
>>
>> But, while running each test file in the for loop, it prepends the name
>> with smoke and hence, it cant find the file and none of the tests in the
>> file are run
>>
>>
>>
>> ~Rajani
>>
>> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
>> abhinandan.prat...@shapeblue.com> wrote:
>>
>>> It is possible, I will check.
>>>
 On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  wrote:

 Hey Abhi,

 In the recent travis runs, its not printing the test case in output (
 https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)

 It used to print the test case name and status (
 https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)

 Do you think it can be due to any recent changes?

 ~Rajani

 On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
 abhinandan.prat...@shapeblue.com> wrote:

>
>   There are more than 10 additional suites that can still be included
>>> to
> the travis-CI.
> Since the current set runs comfortably I will go ahead and add more. If
> the system gets overloaded, then we can balance the kind of test
>>> suites and
> amount of test suits that run comfortably on travis.
>
> -abhi
>
>
>
>
> Find out more about ShapeBlue and our range of CloudStack related
>>> services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework<
>>> http://shapeblue.com/csforge/>
> CloudStack Consulting
> CloudStack Software Engineering<
> http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are
>>> intended
> solely for the use of the individual to whom it is addressed. Any
>>> views or
> opinions expressed are solely those of the author and do not
>>> necessarily
> represent those of Shape Blue Ltd or related companies. If you are not
>>> the
> intended recipient of this email, you must neither take any action
>>> based
> upon its contents, nor copy or show it to anyone. Please contact the
>>> sender
> if you believe you have received this email in error. Shape Blue Ltd
>>> is a
> company incorporated in England & Wales. ShapeBlue Services India LLP
>>> is a
> company incorporated in India and is operated under license from Shape
>>> Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
>>> Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty
>>> Ltd is
> a company registered by The Republic of South Africa and is traded
>>> under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>
>>>
>>> Find out more about ShapeBlue and our range of CloudStack related services
>>>
>>> IaaS Cloud Design & Build<
>>> http://shapeblue.com/iaas-cloud-design-and-build//>
>>> CSForge – rapid IaaS deployment framework
>>> CloudStack Consulting
>>> CloudStack Software Engineering<
>>> http://shapeblue.com/cloudstack-software-engineering/>
>>> CloudStack Infrastructure Support<
>>> http://shapeblue.com/cloudstack-infrastructure-support/>
>>> CloudStack Bootcamp Training Courses<
>>> http://shapeblue.com/cloudstack-training/>
>>>
>>> This email and any attachments to it may be confidential and are intended
>>> solely for the use of the individual to whom it is addressed. Any views or
>>> opinions expressed are solely those of the author and do not necessarily
>>> represent those of Shape Blue Ltd or related companies. If you are not the
>>> intended recipient of this email, you must neither take any action based
>>> upon its contents, nor copy or show it to anyone. Please contact the sender
>>> if you believe you have received this email in error. Shape Blue Ltd is a
>>> company incorporated in England & Wales. ShapeBlue Services India LLP is a
>>> company incorporated in India and is operated under license from Shape Blue
>>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorpor

Re: marvin test cases + travis

[Rajani Karuturi]

after correcting the test file path, its working fine

https://travis-ci.org/karuturi/cloudstack/jobs/60681263



~Rajani

On Thu, Apr 30, 2015 at 4:51 PM, Rajani Karuturi  wrote:

> I think its due to this commit
>
> https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77
>
> Here, test file name is changed from testname to [smoke,component]/testname
>
> But, while running each test file in the for loop, it prepends the name
> with smoke and hence, it cant find the file and none of the tests in the
> file are run
>
>
>
> ~Rajani
>
> On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>> It is possible, I will check.
>>
>> > On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  wrote:
>> >
>> > Hey Abhi,
>> >
>> > In the recent travis runs, its not printing the test case in output (
>> > https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
>> >
>> > It used to print the test case name and status (
>> > https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
>> >
>> > Do you think it can be due to any recent changes?
>> >
>> > ~Rajani
>> >
>> > On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
>> > abhinandan.prat...@shapeblue.com> wrote:
>> >
>> >>
>> >>There are more than 10 additional suites that can still be included
>> to
>> >> the travis-CI.
>> >> Since the current set runs comfortably I will go ahead and add more. If
>> >> the system gets overloaded, then we can balance the kind of test
>> suites and
>> >> amount of test suits that run comfortably on travis.
>> >>
>> >> -abhi
>> >>
>> >>
>> >>
>> >>
>> >> Find out more about ShapeBlue and our range of CloudStack related
>> services
>> >>
>> >> IaaS Cloud Design & Build<
>> >> http://shapeblue.com/iaas-cloud-design-and-build//>
>> >> CSForge – rapid IaaS deployment framework<
>> http://shapeblue.com/csforge/>
>> >> CloudStack Consulting
>> >> CloudStack Software Engineering<
>> >> http://shapeblue.com/cloudstack-software-engineering/>
>> >> CloudStack Infrastructure Support<
>> >> http://shapeblue.com/cloudstack-infrastructure-support/>
>> >> CloudStack Bootcamp Training Courses<
>> >> http://shapeblue.com/cloudstack-training/>
>> >>
>> >> This email and any attachments to it may be confidential and are
>> intended
>> >> solely for the use of the individual to whom it is addressed. Any
>> views or
>> >> opinions expressed are solely those of the author and do not
>> necessarily
>> >> represent those of Shape Blue Ltd or related companies. If you are not
>> the
>> >> intended recipient of this email, you must neither take any action
>> based
>> >> upon its contents, nor copy or show it to anyone. Please contact the
>> sender
>> >> if you believe you have received this email in error. Shape Blue Ltd
>> is a
>> >> company incorporated in England & Wales. ShapeBlue Services India LLP
>> is a
>> >> company incorporated in India and is operated under license from Shape
>> Blue
>> >> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
>> Brasil
>> >> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty
>> Ltd is
>> >> a company registered by The Republic of South Africa and is traded
>> under
>> >> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>> >>
>>
>> Find out more about ShapeBlue and our range of CloudStack related services
>>
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>>
>> This email and any attachments to it may be confidential and are intended
>> solely for the use of the individual to whom it is addressed. Any views or
>> opinions expressed are solely those of the author and do not necessarily
>> represent those of Shape Blue Ltd or related companies. If you are not the
>> intended recipient of this email, you must neither take any action based
>> upon its contents, nor copy or show it to anyone. Please contact the sender
>> if you believe you have received this email in error. Shape Blue Ltd is a
>> company incorporated in England & Wales. ShapeBlue Services India LLP is a
>> company incorporated in India and is operated under license from Shape Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
>> a company registered by The Republic of South Africa and is traded under
>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>
>
>

Re: marvin test cases + travis

[Rajani Karuturi]

I think its due to this commit
https://github.com/apache/cloudstack/commit/b941480e0df0bfa3377e797126b96cf9b3fbee77

Here, test file name is changed from testname to [smoke,component]/testname

But, while running each test file in the for loop, it prepends the name
with smoke and hence, it cant find the file and none of the tests in the
file are run



~Rajani

On Thu, Apr 30, 2015 at 4:37 PM, Abhinandan Prateek <
abhinandan.prat...@shapeblue.com> wrote:

> It is possible, I will check.
>
> > On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  wrote:
> >
> > Hey Abhi,
> >
> > In the recent travis runs, its not printing the test case in output (
> > https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
> >
> > It used to print the test case name and status (
> > https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
> >
> > Do you think it can be due to any recent changes?
> >
> > ~Rajani
> >
> > On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> > abhinandan.prat...@shapeblue.com> wrote:
> >
> >>
> >>There are more than 10 additional suites that can still be included
> to
> >> the travis-CI.
> >> Since the current set runs comfortably I will go ahead and add more. If
> >> the system gets overloaded, then we can balance the kind of test suites
> and
> >> amount of test suits that run comfortably on travis.
> >>
> >> -abhi
> >>
> >>
> >>
> >>
> >> Find out more about ShapeBlue and our range of CloudStack related
> services
> >>
> >> IaaS Cloud Design & Build<
> >> http://shapeblue.com/iaas-cloud-design-and-build//>
> >> CSForge – rapid IaaS deployment framework >
> >> CloudStack Consulting
> >> CloudStack Software Engineering<
> >> http://shapeblue.com/cloudstack-software-engineering/>
> >> CloudStack Infrastructure Support<
> >> http://shapeblue.com/cloudstack-infrastructure-support/>
> >> CloudStack Bootcamp Training Courses<
> >> http://shapeblue.com/cloudstack-training/>
> >>
> >> This email and any attachments to it may be confidential and are
> intended
> >> solely for the use of the individual to whom it is addressed. Any views
> or
> >> opinions expressed are solely those of the author and do not necessarily
> >> represent those of Shape Blue Ltd or related companies. If you are not
> the
> >> intended recipient of this email, you must neither take any action based
> >> upon its contents, nor copy or show it to anyone. Please contact the
> sender
> >> if you believe you have received this email in error. Shape Blue Ltd is
> a
> >> company incorporated in England & Wales. ShapeBlue Services India LLP
> is a
> >> company incorporated in India and is operated under license from Shape
> Blue
> >> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
> Brasil
> >> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd
> is
> >> a company registered by The Republic of South Africa and is traded under
> >> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
> >>
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering<
> http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
> a company registered by The Republic of South Africa and is traded under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>

Re: marvin test cases + travis

[Abhinandan Prateek]

It is possible, I will check.

> On 30-Apr-2015, at 3:43 pm, Rajani Karuturi  wrote:
>
> Hey Abhi,
>
> In the recent travis runs, its not printing the test case in output (
> https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)
>
> It used to print the test case name and status (
> https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)
>
> Do you think it can be due to any recent changes?
>
> ~Rajani
>
> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>>
>>There are more than 10 additional suites that can still be included to
>> the travis-CI.
>> Since the current set runs comfortably I will go ahead and add more. If
>> the system gets overloaded, then we can balance the kind of test suites and
>> amount of test suits that run comfortably on travis.
>>
>> -abhi
>>
>>
>>
>>
>> Find out more about ShapeBlue and our range of CloudStack related services
>>
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>>
>> This email and any attachments to it may be confidential and are intended
>> solely for the use of the individual to whom it is addressed. Any views or
>> opinions expressed are solely those of the author and do not necessarily
>> represent those of Shape Blue Ltd or related companies. If you are not the
>> intended recipient of this email, you must neither take any action based
>> upon its contents, nor copy or show it to anyone. Please contact the sender
>> if you believe you have received this email in error. Shape Blue Ltd is a
>> company incorporated in England & Wales. ShapeBlue Services India LLP is a
>> company incorporated in India and is operated under license from Shape Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
>> a company registered by The Republic of South Africa and is traded under
>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: marvin test cases + travis

[Rajani Karuturi]

Hey Abhi,

In the recent travis runs, its not printing the test case in output (
https://travis-ci.org/apache/cloudstack/jobs/60634577#L5443)

It used to print the test case name and status (
https://travis-ci.org/apache/cloudstack/jobs/59958134#L4205)

Do you think it can be due to any recent changes?

~Rajani

On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
abhinandan.prat...@shapeblue.com> wrote:

>
> There are more than 10 additional suites that can still be included to
> the travis-CI.
> Since the current set runs comfortably I will go ahead and add more. If
> the system gets overloaded, then we can balance the kind of test suites and
> amount of test suits that run comfortably on travis.
>
> -abhi
>
>
>
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering<
> http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
> a company registered by The Republic of South Africa and is traded under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>

Re: marvin test cases + travis

[Abhinandan Prateek]

> On 30-Apr-2015, at 12:05 pm, Rajani Karuturi  wrote:
>
> Hi Abhi,
> Can we also add findbugs check in travis?
>

Let me check the status of findbug, if all the issues are resolved then we can 
make it part of CI.
If not we can make it part of build, and generate and publish the findbug 
reports so that people can fix the issues.

> ~Rajani
>
> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
>
>>
>>There are more than 10 additional suites that can still be included to
>> the travis-CI.
>> Since the current set runs comfortably I will go ahead and add more. If
>> the system gets overloaded, then we can balance the kind of test suites and
>> amount of test suits that run comfortably on travis.
>>
>> -abhi
>>
>>
>>
>>
>> Find out more about ShapeBlue and our range of CloudStack related services
>>
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>>
>> This email and any attachments to it may be confidential and are intended
>> solely for the use of the individual to whom it is addressed. Any views or
>> opinions expressed are solely those of the author and do not necessarily
>> represent those of Shape Blue Ltd or related companies. If you are not the
>> intended recipient of this email, you must neither take any action based
>> upon its contents, nor copy or show it to anyone. Please contact the sender
>> if you believe you have received this email in error. Shape Blue Ltd is a
>> company incorporated in England & Wales. ShapeBlue Services India LLP is a
>> company incorporated in India and is operated under license from Shape Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
>> a company registered by The Republic of South Africa and is traded under
>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>>

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: marvin test cases + travis

[Sebastien Goasguen]

> On Apr 30, 2015, at 8:35 AM, Rajani Karuturi  wrote:
> 
> Hi Abhi,
> Can we also add findbugs check in travis?
> 

note that there are other SaaS services like Travis that we could use…like 
coveralls, tools to create packages etc…

literally any CI/CD can be outsourced...

> ~Rajani
> 
> On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
> abhinandan.prat...@shapeblue.com> wrote:
> 
>> 
>>There are more than 10 additional suites that can still be included to
>> the travis-CI.
>> Since the current set runs comfortably I will go ahead and add more. If
>> the system gets overloaded, then we can balance the kind of test suites and
>> amount of test suits that run comfortably on travis.
>> 
>> -abhi
>> 
>> 
>> 
>> 
>> Find out more about ShapeBlue and our range of CloudStack related services
>> 
>> IaaS Cloud Design & Build<
>> http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Software Engineering<
>> http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure Support<
>> http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses<
>> http://shapeblue.com/cloudstack-training/>
>> 
>> This email and any attachments to it may be confidential and are intended
>> solely for the use of the individual to whom it is addressed. Any views or
>> opinions expressed are solely those of the author and do not necessarily
>> represent those of Shape Blue Ltd or related companies. If you are not the
>> intended recipient of this email, you must neither take any action based
>> upon its contents, nor copy or show it to anyone. Please contact the sender
>> if you believe you have received this email in error. Shape Blue Ltd is a
>> company incorporated in England & Wales. ShapeBlue Services India LLP is a
>> company incorporated in India and is operated under license from Shape Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
>> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
>> a company registered by The Republic of South Africa and is traded under
>> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>> 

Re: marvin test cases + travis

[Rajani Karuturi]

Hi Abhi,
Can we also add findbugs check in travis?

~Rajani

On Thu, Apr 30, 2015 at 10:32 AM, Abhinandan Prateek <
abhinandan.prat...@shapeblue.com> wrote:

>
> There are more than 10 additional suites that can still be included to
> the travis-CI.
> Since the current set runs comfortably I will go ahead and add more. If
> the system gets overloaded, then we can balance the kind of test suites and
> amount of test suits that run comfortably on travis.
>
> -abhi
>
>
>
>
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design & Build<
> http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Software Engineering<
> http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure Support<
> http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses<
> http://shapeblue.com/cloudstack-training/>
>
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is
> a company registered by The Republic of South Africa and is traded under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>

marvin test cases + travis

[Abhinandan Prateek]

There are more than 10 additional suites that can still be included to the 
travis-CI.
Since the current set runs comfortably I will go ahead and add more. If the 
system gets overloaded, then we can balance the kind of test suites and amount 
of test suits that run comfortably on travis.

-abhi




Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Software 
Engineering
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.