Github user 1ambda commented on the issue:

    https://github.com/apache/zeppelin/pull/1639
  
    `grunt serve` and `grunt build` work will but `grunt test` failed. I am not 
sure this is due to the change in this PR
    
    ```
    $ grunt test
    
    ...
    
    Running "karma:unit" (karma) task
    INFO [karma]: Karma v0.12.37 server started at http://localhost:9002/
    INFO [launcher]: Starting browser PhantomJS
    WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.
    INFO [launcher]: Trying to start PhantomJS again (1/2).
    WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.
    INFO [launcher]: Trying to start PhantomJS again (2/2).
    WARN [launcher]: PhantomJS have not captured in 60000 ms, killing.
    ERROR [launcher]: PhantomJS failed 2 times (timeout). Giving up.
    Warning: Task "karma:unit" failed. Use --force to continue.
    
    Aborted due to warnings.
    
    
    Execution Time (2016-11-15 14:28:46 UTC)
    babel:dev           4.8s  ▇▇ 2%
    concurrent:test    17.6s  ▇▇▇▇▇▇ 9%
    karma:unit       3m 0.4s  
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
 88%
    Total 3m 24.5s
    ```
    
    Regarding to `grunt serve` it takes time more than before (i changed some 
`var` keyword to `let` to test this).
    However, I pretty sure that we can reduce build time by using more enhanced 
tools (webpack, upper version babel and node and so on)
    
    ```
    Running "newer:babel:dev" (newer) task
    
    Running "babel:dev" (babel) task
    
    Running 
"newer-postrun:babel:dev:3:/Users/lambda/github/apache-zeppelin/zeppelin-review/zeppelin-web/node_modules/grunt-newer/.cache"
 (newer-postrun) task
    
    Done, without errors.
    
    
    Execution Time (2016-11-15 14:39:16 UTC)
    loading tasks  157ms  ▇▇▇▇ 5%
    eslint:all     275ms  ▇▇▇▇▇▇ 8%
    jscs:all       305ms  ▇▇▇▇▇▇ 9%
    babel:dev       2.7s  
▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇
 77%
    Total 3.5s
    
    ```


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to