I was able to get the build to complete by changing the port in test/karma.conf.js.
Since it starts a server successfully on 9001, I edited the PhantomJS port to use 9002. There will still be an issue if OSX user has a running process listening on port 9002, but at least this is less common than 8080. I'm creating an issue and PR to address this shortly. On Sat, Sep 26, 2015 at 2:36 PM, Randy Gelhausen <rgel...@gmail.com> wrote: > I'm running into the same problem. I'm also using -DskipTests, so I'm not > sure why karma tests are even running. > > Is this something that can be fixed in some way? > > On Fri, Sep 18, 2015 at 2:36 AM, madhuka udantha <madhukaudan...@gmail.com > > wrote: > >> (grunt test) karma is able to pick next port (off set will be +1) >> if default port (8080) is used. >> >> some case karma is not able to find that port 8080 is busy. (not sure how >> mac os handle it) >> >> Wish you all the best for your next steps. >> -- >> Cheers, >> Madhuka Udantha >> http://madhukaudantha.blogspot.com >> > >
