Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148649629
[Test build #1908 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1908/consoleFull)
for PR 9128 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148675198
[Test build #1908 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1908/console)
for PR 9128 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148678251
[Test build #1910 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1910/consoleFull)
for PR 9128 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148704856
[Test build #1910 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1910/console)
for PR 9128 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148717522
[Test build #1915 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1915/consoleFull)
for PR 9128 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148750210
[Test build #1915 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1915/console)
for PR 9128 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148760115
merged to master
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9128
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148360061
I think it's OK, but what does it help? if warnings are to be treated as
errors, they are errors like others. Does it become confusing to log an error
that says "warn"?
Github user jodersky commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148438185
In general I agree with you, however since in this case some warnings (such
as deprecations) are not treated as fatal, the user gets a huge amount of
messages
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148549539
sounds like the behavior is the same with only the prefix "[warn] " added
for non-deprecation warning, which seems like a good idea...
---
If your project is set
Github user jodersky commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148557456
Yeah that's it ;)
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148251261
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
13 matches
Mail list logo
