Github user tsliwowicz closed the pull request at:
https://github.com/apache/spark/pull/2914
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-67545730
By the way can you close this now that is' merged? thanks
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-67383453
Now that the necessary back ports are in place. Jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-67383943
[Test build #24552 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24552/consoleFull)
for PR 2914 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-67397591
[Test build #24552 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24552/consoleFull)
for PR 2914 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-67397605
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-67404758
Finally. I'm merging this into branch-1.0 thanks for your patience
@tsliwowicz
---
If your project is set up for it, you can reply to this email and have your
reply
Github user tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-67451754
hurray :-)
On Thu, Dec 18, 2014 at 12:13 AM, andrewor14 notificati...@github.com
wrote:
Finally. I'm merging this into branch-1.0 thanks for your
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-67096195
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-67096546
[Test build #24475 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24475/consoleFull)
for PR 2914 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-67098531
[Test build #24475 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24475/consoleFull)
for PR 2914 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-67098540
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-67101629
jenkins, test 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 project does not have this
Github user tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66446290
No problem. Glad to help :-)
On Wed, Dec 10, 2014 at 4:44 AM, andrewor14 notificati...@github.com
wrote:
Hey sorry @tsliwowicz
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66514970
Looks like the issue is that in our tests we use python 2.6, and this
version cannot unpickle arrays properly by default. @davies will backport #2365
to branch-1.0
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66540531
The build fix PR is #3668
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66359052
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 this
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66359278
I think this might be an issue with the Jenkins pull request builder and
pull requests that are opened against non-master backport branches. Once this
latest test run
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66359393
[Test build #24260 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24260/consoleFull)
for PR 2914 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66370803
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66370793
[Test build #24260 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24260/consoleFull)
for PR 2914 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66373444
@JoshRosen and I just fixed the test infra failure for older branches.
Let's retest this please
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66373810
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66375507
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66376354
[Test build #24267 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24267/consoleFull)
for PR 2914 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66384322
[Test build #24267 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24267/consoleFull)
for PR 2914 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66384336
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66389142
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 this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66389892
[Test build #24280 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24280/consoleFull)
for PR 2914 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66395752
[Test build #24280 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24280/consoleFull)
for PR 2914 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66395757
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-66396333
Hey sorry @tsliwowicz for using your PRs as the battleground in fixing our
builds against older branches. There aren't a lot of PRs opened against older
branches so
Github user tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-65783784
Seems like an issue with 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 your project does
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-65724015
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-65724800
[Test build #24149 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24149/consoleFull)
for PR 2914 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-65732248
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-65732242
[Test build #24149 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24149/consoleFull)
for PR 2914 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2915#issuecomment-65017464
Hi @tsliwowicz,
It looks like this pull request was merged into `branch-1.1`, but it won't
automatically be closed by GitHub since that commit won't land in
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2915
---
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 tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-60739832
Hi @andrewor14 - can I help somehow? I see that the PRs were not yet merged
into 0.9 and 1.0
---
If your project is set up for it, you can reply to this email and
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-60790265
Yeah I'm a little swamped for the 1.2 release at the moment so I haven't
had time to dig into the Jenkins issue for older branches. I will try to look
into it later
Github user tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-60389844
there seems to be some technical issue with the build. (not a real failure
with the pull request itself)
---
If your project is set up for it, you can reply to this
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-60393584
(Looks like you should close this in favor of your other PR. You don't need
to reopen just to update a PR. Yes the test failure looks unrelated. You can
just ask Jenkins
Github user tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-60410765
I was asked by @andrewor14 to open separate PRs because it does not merge
cleanly. https://github.com/apache/spark/pull/2886 was approved and merged.
---
If your
Github user tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-60411019
@srowen I don't have a login to Jenkins so someone else needs to restart
the build. Is there a way to get a login? I would gladly do it.
---
If your project is set
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-60420357
You should be able to say retest this please and it'll trigger it
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-60421302
[Test build #22146 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22146/consoleFull)
for PR 2914 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2915#issuecomment-60427148
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 this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2915#issuecomment-60428151
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22149/consoleFull)
for PR 2915 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-60431510
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-60431500
[Test build #22146 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22146/consoleFull)
for PR 2914 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2915#issuecomment-60439570
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22149/consoleFull)
for PR 2915 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2915#issuecomment-60439576
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2915#issuecomment-60447381
I'm merging this thanks.
---
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/2914#issuecomment-60447743
There's an issue with Spark running tests on PRs opened against older
branches (e.g. 1.0, 0.9). I will look into this shortly...
---
If your project is set up for
Github user tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-60448957
@andrewor14 - thanks for your help!
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60220879
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22070/consoleFull)
for PR 2886 at commit
Github user tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60221362
@andrewor14 - thanks for the comments. I believe I fixed them all. Let me
know!
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60221739
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22072/consoleFull)
for PR 2886 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60222452
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60222733
the failure seems technical (not related to my fix), I think. Local maven
build works fine for me.
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60227754
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22070/consoleFull)
for PR 2886 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60227762
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60228517
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60228510
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22072/consoleFull)
for PR 2886 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/2886#discussion_r19294252
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerMasterActor.scala ---
@@ -325,22 +325,23 @@ class BlockManagerMasterActor(val isLocal:
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60279888
Ok I have merged this into master. It doesn't merge cleanly into 1.1, so
@tsliwowicz can you create a new PR against that branch? Thanks.
---
If your project is set
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60280998
(also branch 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 not have this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2886
---
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 tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60306506
will do. Can you also merge into the 0.9 branch? I will update the PR I
already have for it. https://github.com/apache/spark/pull/2854
---
If your project is set up
GitHub user tsliwowicz opened a pull request:
https://github.com/apache/spark/pull/2914
[SPARK-4006] In long running contexts, we encountered the situation of d...
...ouble registe...
...r without a remove in between. The cause for that is unknown, and
assumed a temp
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-60311859
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22086/consoleFull)
for PR 2914 at commit
GitHub user tsliwowicz opened a pull request:
https://github.com/apache/spark/pull/2915
[SPARK-4006] In long running contexts, we encountered the situation of d...
...ouble registe...
...r without a remove in between. The cause for that is unknown, and
assumed a temp
Github user tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60312692
@andrewor14 I created PR for 1.0, 1.1 and updated the 0.9 PR - can you
please review and merge if ok?
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2915#issuecomment-60313119
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22087/consoleFull)
for PR 2915 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60313702
Thanks a lot @tsliwowicz I'll do that shortly.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-60320994
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22086/consoleFull)
for PR 2914 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2914#issuecomment-60321003
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2915#issuecomment-60325586
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2915#issuecomment-60325584
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22087/consoleFull)**
after a configured wait of `120m`.
---
If your project
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/2886#discussion_r19249767
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerMasterActor.scala ---
@@ -325,22 +325,23 @@ class BlockManagerMasterActor(val isLocal:
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/2886#discussion_r19249800
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerMasterActor.scala ---
@@ -325,22 +325,23 @@ class BlockManagerMasterActor(val isLocal:
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/2886#discussion_r19249967
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerMasterActor.scala ---
@@ -325,22 +325,23 @@ class BlockManagerMasterActor(val isLocal:
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/2886#discussion_r19250038
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerMasterActor.scala ---
@@ -325,22 +325,23 @@ class BlockManagerMasterActor(val isLocal:
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/2886#discussion_r19250102
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerMasterActor.scala ---
@@ -203,6 +202,7 @@ class BlockManagerMasterActor(val isLocal:
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60168995
Hey @tsliwowicz there are a few style and wording issues that I'd like to
see fixed. Also, I would prefer to have the whitespace changes reverted.
However, I think
GitHub user tsliwowicz opened a pull request:
https://github.com/apache/spark/pull/2886
[SPARK-4006] In long running contexts, we encountered the situation of
double registe...
...r without a remove in between. The cause for that is unknown, and
assumed a temp network issue.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60018087
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60019018
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 this feature
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60019511
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22016/consoleFull)
for PR 2886 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60024276
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2886#issuecomment-60024273
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/22016/consoleFull)
for PR 2886 at commit
92 matches
Mail list logo
