Hi.
I am trying to install Zeppelin and so far this didn't work for me.
I am sure this is just my own stupidity, but still could you please point
me in the right direction?
I tried a couple of different things, but to make things simple I ran a
scenario again that I suspect should be fairly comm
Hi,
thank you for interest in Zeppelin!
It looks like frontend webapp build failed on executing the grunt task (a
build system we use in web app). Can you try running it manually (instead
of using maven)
```
cd zepelin-web
./grunt
```
and let me know if that works?
It suppose to print smth lik
This happened a few times recently (even on CI)
Running it manually in the folder always works, but tends to fails without
error (kinda time out) from maven.
You can try to clean and run it again
On Fri, Sep 18, 2015 at 12:16 PM, Alexander Bezzubov
wrote:
> Hi,
>
> thank you for interest in Zepp
Thank you Alex.
Zeppelin looks awesome.
It seems to also fail manually:
snow:incubator-zeppelin mkamp$ cd zeppelin-web/
snow:zeppelin-web mkamp$ ./grunt
Running "newer:jshint" (newer) task
Running "newer:jshint:all" (newer) task
No newer files to process.
Running "newer:jshint:test" (newe
Thanks. It seems to fail every time.
I googled a bit and found a couple of different causes. The short version
is something was wrong on my machine and 8080 was already used and didn't
lead to a good error message.
The longer version starts here:
http://www.panozzaj.com/blog/2015/02/28/debugging-
Good to know, thank you for sharing,
may be it worth changing defaults to a different port, which has less
probability of being busy.
Wish you a good luck for your further research!
--
Kind regards,
Alexander
> On 18 Sep 2015, at 15:08, Mariano Kamp wrote:
>
> Thanks. It seems to fail every
(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
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
wrote:
> (grunt test) karma is able to pick next port (off set will be +1)
> if def
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 8
