Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/3177#issuecomment-62517262
Jenkins, this is ok to 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3177#issuecomment-62517782
[Test build #23212 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23212/consoleFull)
for PR 3177 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3177#issuecomment-62527255
[Test build #23212 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/23212/consoleFull)
for PR 3177 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3177#issuecomment-62527264
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/3177#issuecomment-62527448
@maji2014 Thanks for this fix. Merging this.
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3177
---
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
Github user maji2014 commented on the pull request:
https://github.com/apache/spark/pull/3177#issuecomment-62363954
Yes, the test cases are all passed although exception throws before each
test case.
you can run SparkSinkSuite.scala directly and know the appearance like
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/3177#issuecomment-62491505
@maji2014 Correct, I verified this error after adding a log4j properties in
the `external/flume-sink/src/test/resources` and seeing the log4j logs. And
manually verified
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/3177#discussion_r20128469
--- Diff:
external/flume-sink/src/test/scala/org/apache/spark/streaming/flume/sink/SparkSinkSuite.scala
---
@@ -159,6 +159,7 @@ class SparkSinkSuite extends
Github user harishreedharan commented on a diff in the pull request:
https://github.com/apache/spark/pull/3177#discussion_r20129588
--- Diff:
external/flume-sink/src/test/scala/org/apache/spark/streaming/flume/sink/SparkSinkSuite.scala
---
@@ -159,6 +159,7 @@ class SparkSinkSuite
Github user maji2014 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3177#discussion_r20130942
--- Diff:
external/flume-sink/src/test/scala/org/apache/spark/streaming/flume/sink/SparkSinkSuite.scala
---
@@ -159,6 +159,7 @@ class SparkSinkSuite
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/3177#discussion_r20130997
--- Diff:
external/flume-sink/src/test/scala/org/apache/spark/streaming/flume/sink/SparkSinkSuite.scala
---
@@ -159,6 +159,7 @@ class SparkSinkSuite extends
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/3177#discussion_r20131009
--- Diff:
external/flume-sink/src/test/scala/org/apache/spark/streaming/flume/sink/SparkSinkSuite.scala
---
@@ -159,6 +159,7 @@ class SparkSinkSuite extends
Github user maji2014 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3177#discussion_r20132263
--- Diff:
external/flume-sink/src/test/scala/org/apache/spark/streaming/flume/sink/SparkSinkSuite.scala
---
@@ -159,6 +159,7 @@ class SparkSinkSuite
GitHub user maji2014 opened a pull request:
https://github.com/apache/spark/pull/3177
[SPARK-4295][External]Fix exception in SparkSinkSuite
Handle exception in SparkSinkSuite, please refer to [SPARK-4295]
You can merge this pull request into a Git repository by running:
$ git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3177#issuecomment-62308120
Can one of the admins verify this patch?
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/3177#issuecomment-62321381
Can you clarify how the tests pass if an exception is thrown? does that
also need a fix?
---
If your project is set up for it, you can reply to this email and have your
17 matches
Mail list logo
