Sorry. You run them like this:
$ mvn verify -P native
The integration tests take about 50 minutes when all is working well. I
hope to be able to run them in parallel but so far, I've not had any luck.
On Tue, Jul 23, 2013 at 8:45 PM, Michael Berman <[EMAIL PROTECTED]> wrote:
> I was asking how to run them, not how to skip them. I'm not planning on
> running them all the time, but I'd like to know I'm not breaking them
> before I push changes :-)
> Ok great Eric. I'm not at my workstation right now, but I'll send you my
> error list and specs tonight or tomorrow. Just for ballpark, it's an 8
> monthish old, high-end MacBook Pro with 16G RAM. It's a laptop, so it's
> not the beefiest machine, but it's certainly not anemic.
> On Tue, Jul 23, 2013 at 7:27 PM, Eric Newton <[EMAIL PROTECTED]>
> > I would like feedback on what is failing so I can look into it. I have
> > them all run, but it's still pretty rare.
> > Can you give me an idea of what your local hardware is like?
> > Christopher gave me a great suggestion the other day: run these tests
> > an anemic virtual host, which I plan to do.
> > Please know I'm working on it, and I would like any help I can get.
> > -Eric
> > On Tue, Jul 23, 2013 at 6:25 PM, Christopher <[EMAIL PROTECTED]>
> > > Try running them with -P native. Eric has been working on improving
> > >
> > > --
> > > Christopher L Tubbs II
> > > http://gravatar.com/ctubbsii
> > >
> > >
> > > On Tue, Jul 23, 2013 at 5:46 PM, Michael Berman <[EMAIL PROTECTED]>
> > wrote:
> > > > Does anyone have any advice for running integration tests locally?
> > > the
> > > > moment a large number of them time out for me, and others have
> > assertion
> > > > failures that aren't obviously due to my running them locally, but
> > > > assuming it is because no one else seems to be complaining (of course
> > > since
> > > > there hasn't been a successful Jenkins build in like three weeks,
> > > > it's just that no one's noticed).
> > >