You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by Madhuka <gi...@git.apache.org> on 2015/08/04 12:44:23 UTC
[GitHub] incubator-zeppelin pull request: ZEPPELIN-161 : Ffixing grunt test
GitHub user Madhuka opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/179
ZEPPELIN-161 : Ffixing grunt test
All the test in zeppelin web was failed. Contain older version code
Here is the fixed.
- [x] Fixing Karma config
- [x] Handle js file paths in Karma config in atomically
- [x] Fixing config properties
- [x] Updating test spec for current code base version
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Madhuka/incubator-zeppelin milestone06-test-new
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/179.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #179
----
commit 4a9d64af54883d792b2604ebae3627f391587b03
Author: madhuka <ma...@gmail.com>
Date: 2015-08-04T10:40:36Z
fixing grunt test
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: ZEPPELIN-161 : Ffixing grunt test
Posted by Madhuka <gi...@git.apache.org>.
Github user Madhuka commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/179#issuecomment-127586204
When I check builder log web application was build successfully
End of the log I found
11:01:42,552 INFO org.apache.zeppelin.notebook.Paragraph:211 - RUN : from pyspark.sql.functions import *
print(sqlContext.range(0, 10).withColumn('uniform', rand(seed=10) * 3.14).count())
No output has been received in the last 10 minutes, this potentially indicates a stalled build or something wrong with the build itself.
The build has been terminated
is it builder resource issue? or Env? any idea?
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: ZEPPELIN-161 : Fixing grunt test
Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/179#issuecomment-129235422
Thanks for great contribution. LGTM!
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: ZEPPELIN-161 : Fixing grunt test
Posted by Madhuka <gi...@git.apache.org>.
Github user Madhuka commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/179#issuecomment-127885084
`./grunt buildSkipTests` will build without test. It can be used in CI
![grunt-buildskiptests](https://cloud.githubusercontent.com/assets/1180128/9079448/d5686208-3b67-11e5-93ff-3418c1c0b49c.png)
`./grunt build` will contain the test
![grunt-build](https://cloud.githubusercontent.com/assets/1180128/9079452/db46a784-3b67-11e5-872b-340c4e9d7a2a.png)
`./grunt test` will run all the test specs
![grunt-test](https://cloud.githubusercontent.com/assets/1180128/9079456/dfcdc418-3b67-11e5-9291-a56f11bea53d.png)
JIRA[1] is created for integrating those to CI
[1] https://issues.apache.org/jira/browse/ZEPPELIN-166
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: ZEPPELIN-161 : Fixing grunt test
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/179
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-zeppelin pull request: ZEPPELIN-161 : Fixing grunt test
Posted by Madhuka <gi...@git.apache.org>.
Github user Madhuka commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/179#issuecomment-129186977
@Leemoonsoo : Ready for Merge
@bzz, @corneadoug This contain the fixed for grunt test.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---