Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Sat, 6 Apr 2013 13:16:05 -0400
From: Chip Childers <chip.childers@sungard.com>
To: dev@cloudstack.apache.org
Subject: Re: Master broken
Message-ID: <20130406171605.GA45212@USLT-205755.sungardas.corp>
References: 
 <B1DF26ECC0458748AC97CECE2DA98D410143EB525D4C@SJCPMAILBOX01.citrite.net>
 <3BCE9BB272306B449A3BD520DD47A79603286C@SINPEX01CL02.citrite.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3BCE9BB272306B449A3BD520DD47A79603286C@SINPEX01CL02.citrite.net>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Sat, Apr 06, 2013 at 05:27:11AM +0000, Prasanna Santhanam wrote:
> Ah - misunderstood. Like Hugo said, a test that fails on presence of db connection should solve this. But I hope ppl will turn mysql on (as an additional step) to run the bvt. Or better yet, I can look into those db tests and port them as marvin tests.
> 

Perhaps I'm confused, but having a unit test that fails the build if
MySQL is running on the local machine seems like a really bad idea.

I think the problem to solve is just that we want to avoid unit tests
that require a DB.  As long as we all know this, and that we have build
jobs that fail on the CI side of things, isn't that enough?

Am I confused?

> 
> 
> 
> --
> Prasanna.,
> 
> ----- Original Message -----
> From: Alex Huang [mailto:Alex.Huang@citrix.com]
> Sent: Saturday, April 06, 2013 05:21 AM
> To: dev@cloudstack.apache.org <dev@cloudstack.apache.org>
> Subject: RE: Master broken
> 
> > That will be hard to do since the checkin test requires the DB to be present as
> > it starts up the server and sets-up the databases. We'd have to turn it off for
> > the build and turn it back on again for the bvt. Best if we avoid doing -
> > DskipTests when building as a general good rule.
> 
> I don't think -DskipTests is the problem.  The problem is actually people who are running the unit tests have db on their laptops so if they have unit tests that require DB will run on their laptop but fails on Jenkins, which doesn't have a db.
> 
> --Alex
>