[GitHub] zeppelin issue #2341: ZEPPELIN-2543: Add ability to change the log level at ...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/2341 Thanks @karuppayya for the contribution! LGTM and merge to master if no further comments. --- 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. ---
[GitHub] zeppelin issue #2341: ZEPPELIN-2543: Add ability to change the log level at ...
Github user karuppayya commented on the issue: https://github.com/apache/zeppelin/pull/2341 @1ambda Thanks for the feedback. I had added API to Zeppelin rest API name space. Let me know if that is fine Also adding documentation was in my TODO list, done now. --- 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. ---
[GitHub] zeppelin issue #2341: ZEPPELIN-2543: Add ability to change the log level at ...
Github user 1ambda commented on the issue: https://github.com/apache/zeppelin/pull/2341 IMO, we can add documentation for this API in http://zeppelin.apache.org/docs/0.7.1/rest-api/rest-configuration.html --- 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. ---
[GitHub] zeppelin issue #2341: ZEPPELIN-2543: Add ability to change the log level at ...
Github user karuppayya commented on the issue: https://github.com/apache/zeppelin/pull/2341 I renamed my repo from incubator-zeppelin to zeppelin, and force pushed a commit. Then Jenkins started running the build.(Not sure if it was the rename that made it work) One of the build [job](https://s3.amazonaws.com/archive.travis-ci.org/jobs/233987208/log.txt?X-Amz-Expires=30=20170519T142353Z=AWS4-HMAC-SHA256=AKIAJRYRXRSVGNKPKO5A/20170519/us-east-1/s3/aws4_request=host=7771d2f7d106140e0734a766653da48db3fd1be63e5cb88543c16e9fcace9e66) failed(timed out). Seems not relevant to my change. --- 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. ---
[GitHub] zeppelin issue #2341: ZEPPELIN-2543: Add ability to change the log level at ...
Github user karuppayya commented on the issue: https://github.com/apache/zeppelin/pull/2341 Appveyor link shows as build ran https://ci.appveyor.com/project/ApacheSoftwareFoundation/zeppelin/build/1.0.0-dev.257 Jenkins still shows as error(saying **travis-ci is not configured for your fork**) Otherwise, Ready for review --- 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. ---
[GitHub] zeppelin issue #2341: ZEPPELIN-2543: Add ability to change the log level at ...
Github user karuppayya commented on the issue: https://github.com/apache/zeppelin/pull/2341 Checked the page, And i see a build had ran . Not sure why *jenkin* shows a x icon in github page, though the build runs. --- 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. ---
[GitHub] zeppelin issue #2341: ZEPPELIN-2543: Add ability to change the log level at ...
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/2341 Did you see zeppelin in your travis page ? Go to https://travis-ci.org/ to check that. --- 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. ---
[GitHub] zeppelin issue #2341: ZEPPELIN-2543: Add ability to change the log level at ...
Github user karuppayya commented on the issue: https://github.com/apache/zeppelin/pull/2341 I followed the steps in http://zeppelin.apache.org/contribution/contributions.html#continuous-integration. But still get the following error - [2017-05-15 04:48:28] Author: karuppayya, commit: d87780a88d4d3bb50783650692018d410b1b0d04 [2017-05-15 04:48:28] [2017-05-15 04:48:33] Get build status ... [2017-05-15 04:48:33] Can't find build for commit d87780a88d4d3bb50783650692018d410b1b0d04 from karuppayya RET_CODE=2 '[' 2 -eq 2 ']' set +x - Looks like travis-ci is not configured for your fork. - Add ideas what i could be missing @Leemoonsoo @zjffdu --- 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. ---
[GitHub] zeppelin issue #2341: ZEPPELIN-2543: Add ability to change the log level at ...
Github user karuppayya commented on the issue: https://github.com/apache/zeppelin/pull/2341 Closing it and reopening to trigger CI --- 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. ---
