Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/290#issuecomment-40050337
Merged build finished.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/268#issuecomment-40050336
Build finished. All automated tests passed.
---
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 p
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/268#issuecomment-40050338
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13986/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/290#issuecomment-40050339
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13985/
---
If your project is set up for it, you can r
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/325#discussion_r11473388
--- Diff: core/src/main/scala/org/apache/spark/Logging.scala ---
@@ -135,4 +136,6 @@ trait Logging {
private object Logging {
@volatile private var
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40050637
@witgo I gave an example of using reflection - mind adjusting your patch
and checking if this works?
---
If your project is set up for it, you can reply to this email an
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40050720
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13988/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40050718
Merged build finished.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40050675
Jenkins, retest this please.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40050781
Tests pass locally for me
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/246#issuecomment-40050758
Jenkins is listing some style errors - mind fixing them?
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13987/
---
If your project is set up for i
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/370#issuecomment-40050821
Thanks for the clean-up - looks good! I'm 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40050925
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40050917
Merged build triggered.
---
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 ha
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40051022
I'm guessing it's something random. I'll merge this as soon as it passes.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40051269
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13989/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40051268
Merged build finished.
---
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 yinxusen commented on the pull request:
https://github.com/apache/spark/pull/268#issuecomment-40051673
@mateiz I have fixed the issues. You can merge it if looks good to you.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/363#issuecomment-40051898
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13990/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/363#issuecomment-40051897
Merged build finished.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40052042
Jenkins, test this please.
---
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40052034
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13991/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40052033
Merged build finished.
---
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 witgo commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40052128
@pwendell
Thank you, this patch works
But this only solve one problem. The Spark the dependence of the is fixed,
we can only use log4j.
In SparkBuild.s
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40052187
Merged build triggered.
---
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40052200
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/364#issuecomment-40053172
Merged build triggered.
---
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/364#issuecomment-40053180
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/364#issuecomment-40053227
Merged build finished.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40053228
Merged build finished.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40053712
Jenkins, retest this please (sorry I rebooted jenkins).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/364#issuecomment-40053686
Jenkins, test this please. (sorry I rebooted jenkins).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40053882
Jenkins, test this please.
---
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40053909
Merged build triggered.
---
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/364#issuecomment-40053905
Merged build triggered.
---
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40053913
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/364#issuecomment-40053912
Merged build started.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40054373
no we don't need to change the dependencies. The case I wanted to handle
was if users downstream remove the dependencies (e.g. they remove
"jul-to-slf4j") and do a custom
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40055267
Jenkins, test this please.
---
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40055287
Merged build triggered.
---
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40055296
Merged build started.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/189#issuecomment-40057817
Hey @mateiz @willb @andrewor14 @mengxr,
I've been trying to investigate a bunch of Jenkins failures in other pull
requests and I believe they might be a result of
Github user techaddict closed the pull request at:
https://github.com/apache/spark/pull/370
---
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 e
Github user techaddict commented on the pull request:
https://github.com/apache/spark/pull/370#issuecomment-40059016
@pwendell after this commit i saw there are too many whitespaces in the
codebase, i've managed to fix them all, should i build a pull request for them ?
---
If your pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40059898
Merged build finished.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40059933
Jenkins, test this please.
---
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/364#issuecomment-40059907
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13994/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/364#issuecomment-40059906
Merged build finished.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40059900
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13996/
---
If your project is set up for it, you can r
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/364#issuecomment-40059961
Jenkins, test this please.
---
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 t
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40059950
Jenkins, test this please.
---
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/364#issuecomment-40060058
Merged build triggered.
---
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40060060
Merged build triggered.
---
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40060066
Merged build triggered.
---
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40060096
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/364#issuecomment-40060068
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40060072
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40060333
Merged build finished.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40060334
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13995/
---
If your project is set up for it, you can r
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/189#issuecomment-40060812
Okay - confirmed this was the issue. There was a brief period where Jenkins
was giving false positives on tests, the test result on this PR from 6 days ago
was likely dur
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/378
[SQL] Improve column pruning in the optimizer.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/marmbrus/spark columnPruning
Alternatively you c
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/364#issuecomment-40062918
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40062917
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40062919
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13998/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40062916
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/364#issuecomment-40062921
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13997/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40062920
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13999/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/378#issuecomment-40063021
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/378#issuecomment-40063013
Merged build triggered.
---
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/378#issuecomment-40065726
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/378#issuecomment-40065728
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14000/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-40068650
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-40068637
Merged build triggered.
---
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 ha
Github user CodingCat commented on a diff in the pull request:
https://github.com/apache/spark/pull/186#discussion_r11480540
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1128,13 +986,160 @@ class DAGScheduler(
}
def stop()
Github user willb commented on the pull request:
https://github.com/apache/spark/pull/189#issuecomment-40070735
@pwendell That's odd, since I didn't see any failures locally either. I
haven't rebased this branch in a while, though, so I can check again. Can you
send me a link to the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-40071308
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-40071309
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14001/
---
If your project
Github user AndreSchumacher commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40072003
I'm seeing some Akka related problems in my local build but nothing that
would seem related to this PR. The log forwarding seems to work.
@pwendell thanks
Github user willb commented on the pull request:
https://github.com/apache/spark/pull/189#issuecomment-40086624
OK, I found a couple of failures after rebasing. I'll look at this today
and figure out where things are going wrong. Thanks, and sorry for the
confusion!
---
If your pr
Github user tyro89 commented on the pull request:
https://github.com/apache/spark/pull/371#issuecomment-40095820
Not sure why the build is failing as I'm pretty sure this change isn't
touching any of those two things.
---
If your project is set up for it, you can reply to this email
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/186#discussion_r11491580
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1128,13 +986,160 @@ class DAGScheduler(
}
def stop(
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/379
[WIP] Add the lifecycle interface
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark service
Alternatively you can review and apply the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/379#issuecomment-40105380
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 proj
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/356#issuecomment-40107176
This seems to be failing tests unfortunately -- click through to the
Jenkins log. This is what it says:
```
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/356#issuecomment-40107316
This is why it would be good to add a test actually. For instance you can
add a test with
`_deserialize_double_vector(_serialize_double_vector(array([1,2,3]))` and check
t
Github user techaddict commented on the pull request:
https://github.com/apache/spark/pull/356#issuecomment-40110285
New to spark don't know what's the standard way of adding tests
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
Github user CodingCat commented on a diff in the pull request:
https://github.com/apache/spark/pull/186#discussion_r11494987
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1128,13 +986,160 @@ class DAGScheduler(
}
def stop()
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/356#issuecomment-40111891
Merged build triggered.
---
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/356#issuecomment-40111911
Merged build started.
---
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 techaddict commented on the pull request:
https://github.com/apache/spark/pull/356#issuecomment-40112564
@mateiz done working now :+1:
---
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/371#issuecomment-40114188
Jenkins, retest this please.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40114262
@AndreSchumacher it's likely related to an accidental merge of a buggy
patch into master... try rebasing to the latest master which includes a
reversion of the bug.
---
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/379#issuecomment-40114235
Is there an accompanying JIRA? Could you add a brief summary and/or a
motivation?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40114453
Okay thanks, merged!
---
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 fe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/371#issuecomment-40114603
Merged build triggered.
---
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/371#issuecomment-40114616
Merged build started.
---
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 techaddict opened a pull request:
https://github.com/apache/spark/pull/380
Remove Unnecessary Whitespace's
stack these together in a commit else they show up chunk by chunk in
different commits.
You can merge this pull request into a Git repository by running:
$ gi
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/204#issuecomment-40114842
Thanks, merged into master and 1.0.
---
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 n
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/380#issuecomment-40115151
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 proj
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/325
---
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 enabl
1 - 100 of 426 matches
Mail list logo
