Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12135
Merged build finished. Test FAILed.
---
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16233
Merged build finished. Test FAILed.
---
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15240
Merged build finished. Test FAILed.
---
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15324
Merged build finished. Test FAILed.
---
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16233
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70806/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15240
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70804/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12135
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70805/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16371
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70801/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15324
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70803/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15324
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70802/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15324
Merged build finished. Test FAILed.
---
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16371
Merged build finished. Test FAILed.
---
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16233
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70800/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16320
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70798/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15880
Merged build finished. Test FAILed.
---
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16448
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70796/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16320
Merged build finished. Test FAILed.
---
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16233
Build finished. Test FAILed.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16448
Merged build finished. Test FAILed.
---
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15880
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70797/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15240
**[Test build #70807 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70807/testReport)**
for PR 15240 at commit
[`26b03b2`](https://github.com/apache/spark/commit/26
Github user azmras commented on the issue:
https://github.com/apache/spark/pull/16429
after applying patch can you try to run
sc.parallelize(range(100), 8)
and confirm that it is working, because for me it is not...
and serialisation of objects goes crazy..
had to
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/15671
ping @sethah @jkbradley
---
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 w
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16422
**[Test build #70808 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70808/testReport)**
for PR 16422 at commit
[`4a68ed6`](https://github.com/apache/spark/commit/4a
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/16028
cc @yanboliang
---
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,
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16320
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 feature
enabled and wishes
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16320
**[Test build #70809 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70809/testReport)**
for PR 16320 at commit
[`e59631b`](https://github.com/apache/spark/commit/e5
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16320
I see, @gatorsmile . I will try to make a PR to improve the coverage.
For this issue, the failure about the last commit (adding test case) was a
R failure. So, it's irrelevant. I rerun
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16429
Thanks for your interests @azmras. I just checked it as below:
```python
sc.parallelize(range(100), 8)
```
```
Traceback (most recent call last):
File ".../spa
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16429
Hi @joshrosen and @davies, do you think that should be ported in this PR? I
am worried of making this PR harder by porting it here.
---
If your project is set up for it, you can reply to this e
Github user vpchelko commented on the issue:
https://github.com/apache/spark/pull/16374
We dont use windows operations (Kafka streaming) - so we don't need 'old'
RDDs :)
I need to double check if spark.memory.fraction help to us.
---
If your project is set up for it, you can
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16426
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 feature
enabled and wishes so, or i
Github user paragpc commented on the issue:
https://github.com/apache/spark/pull/11867
Hi @zsxwing,
I have updated the PR. Can you kindly verify 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16426
---
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 ena
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/15324
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 this feature
enabled an
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16028#discussion_r94380581
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -421,6 +435,18 @@ object LinearRegression extends
DefaultParamsRe
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16028#discussion_r94380454
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/MultilayerPerceptronClassifier.scala
---
@@ -101,7 +100,7 @@ private[classification] trait
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16371
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 feature
enabled and wishes so, o
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16371
**[Test build #70810 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70810/testReport)**
for PR 16371 at commit
[`15a10ee`](https://github.com/apache/spark/commit/15
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15324
**[Test build #70811 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70811/testReport)**
for PR 15324 at commit
[`df29d10`](https://github.com/apache/spark/commit/df
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15240
**[Test build #70807 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70807/testReport)**
for PR 15240 at commit
[`26b03b2`](https://github.com/apache/spark/commit/2
Github user zhengruifeng commented on a diff in the pull request:
https://github.com/apache/spark/pull/16028#discussion_r94382491
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -421,6 +435,18 @@ object LinearRegression extends
DefaultPa
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15240
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70807/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15240
Merged build finished. Test FAILed.
---
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
e
Github user zhengruifeng commented on a diff in the pull request:
https://github.com/apache/spark/pull/16028#discussion_r94382823
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/MultilayerPerceptronClassifier.scala
---
@@ -101,7 +100,7 @@ private[classification]
Github user zhengruifeng closed the pull request at:
https://github.com/apache/spark/pull/11303
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16422
**[Test build #70808 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70808/testReport)**
for PR 16422 at commit
[`4a68ed6`](https://github.com/apache/spark/commit/4
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16422
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70808/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16422
Merged build finished. Test 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 project does not have this feature
e
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16455
Better idea: grep for all instances of repeated words and fix more than
just this in one go. I actually see quite a few. This is a quick and dirty grep
that shows most of them `grep -rE "[^m] ([a-zA-
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16456
I don't know that this is the right way to fix it. The fundamental problem
is that the heartbeat message shouldn't block on this.
Also, it might be simpler to do this in parallel rather than
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15324
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70811/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15324
Merged build finished. Test 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 project does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15324
**[Test build #70811 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70811/testReport)**
for PR 15324 at commit
[`df29d10`](https://github.com/apache/spark/commit/d
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16440#discussion_r94389443
--- Diff:
sql/hive-thriftserver/src/main/scala/org/apache/spark/sql/hive/thriftserver/SparkExecuteStatementOperation.scala
---
@@ -111,9 +115,15 @@ private[h
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16320
**[Test build #70809 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70809/testReport)**
for PR 16320 at commit
[`e59631b`](https://github.com/apache/spark/commit/e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16320
Merged build finished. Test 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 project does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16320
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70809/
Test PASSed.
---
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15018
Ping @neggert
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16196
See the discussion above; I think the request is to back out much of this
and leave only the clearly correct improvements like
https://github.com/apache/spark/pull/16196#discussion_r91270660 There ar
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16429
Hi @azmras, now it should work fine for your case as well.
---
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 no
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/12135
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 this feature
enabled an
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16429
**[Test build #70812 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70812/testReport)**
for PR 16429 at commit
[`7b96546`](https://github.com/apache/spark/commit/7b
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12135
**[Test build #70813 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70813/testReport)**
for PR 12135 at commit
[`1b2df22`](https://github.com/apache/spark/commit/1b
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/16371
LGTM
---
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 fe
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16429
**[Test build #70812 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70812/testReport)**
for PR 16429 at commit
[`7b96546`](https://github.com/apache/spark/commit/7
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16429
Merged build finished. Test 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 project does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16429
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70812/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16371
**[Test build #70810 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70810/testReport)**
for PR 16371 at commit
[`15a10ee`](https://github.com/apache/spark/commit/1
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16371
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70810/
Test PASSed.
---
Github user liujianhuiouc commented on the issue:
https://github.com/apache/spark/pull/16456
yes, the root cause is the heartbeat message blockedï¼the Heartbeat could
be send in parallel, but in any way, the deleting of the app's directories
should be async
---
If your project is
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16371
Merged build finished. Test 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 project does not have this feature
e
Github user liujianhuiouc commented on the issue:
https://github.com/apache/spark/pull/16456
add another thread to send heartbeat in parallel, and also remove the part
of deleting directories in async
---
If your project is set up for it, you can reply to this email and have your
rep
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16456
My point is that this is an ad-hoc band-aid for one type of message, and
not really a solution to other messages blocking a heartbeat. IT's probably
best to fix this for real if at all.
If a
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/16457
[SPARK-19057][ML] Instances' weight must be non-negative
## What changes were proposed in this pull request?
1, add non-negative checking in `Instance`
2, fix doc
## How was th
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16457
The doc fixes look unrelated; let's exclude those?
There are many weight fields/args in .ml that should probably also be
checked -- would you please skim them and see if there are other obviously
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16457
**[Test build #70814 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70814/testReport)**
for PR 16457 at commit
[`c99293c`](https://github.com/apache/spark/commit/c9
Github user liujianhuiouc closed the pull request at:
https://github.com/apache/spark/pull/16406
---
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
GitHub user liujianhuiouc opened a pull request:
https://github.com/apache/spark/pull/16458
[SPARK-19001] [Deploy]don't submit sendHeartbeat task again if has
registered
â¦ed runnable
## What changes were proposed in this pull request?
when first successfully regi
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16458
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 project does not have this feat
GitHub user shimingfei opened a pull request:
https://github.com/apache/spark/pull/16459
[MINOR] LauncherState should be only set to SUBMITTED after the application
is submitted
## What changes were proposed in this pull request?
LauncherState should be only set to SUBMITTED aft
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/16460
[SPARK-19058][SQL] fix partition related behaviors with
DataFrameWriter.saveAsTable
## What changes were proposed in this pull request?
When we append data to a partitioned table with
`
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16460
cc @ericl @gatorsmile @yhuai
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16460
**[Test build #70815 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70815/testReport)**
for PR 16460 at commit
[`7f4f360`](https://github.com/apache/spark/commit/7f
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16459
**[Test build #70816 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70816/testReport)**
for PR 16459 at commit
[`312fb9c`](https://github.com/apache/spark/commit/31
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16459
Merged build finished. Test 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 project does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16459
**[Test build #70816 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70816/testReport)**
for PR 16459 at commit
[`312fb9c`](https://github.com/apache/spark/commit/3
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16459
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70816/
Test PASSed.
---
Github user azmras commented on the issue:
https://github.com/apache/spark/pull/16429
Thanks.. it worked...
while you are at it...
sc.parallelize(range(1000), 20).take(5)
is problemetic..
Will be thankful if you can look into it..
---
If your project is set up fo
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16459
(This would require a JIRA)
CC @vanzin or @steveloughran ?
---
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 issue:
https://github.com/apache/spark/pull/16457
**[Test build #70814 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70814/testReport)**
for PR 16457 at commit
[`c99293c`](https://github.com/apache/spark/commit/c
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16457
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70814/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16457
Merged build finished. Test 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 project does not have this feature
e
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16429
@azmras Could you maybe double check? It works okay in my local as below:
```
Welcome to
__
/ __/__ ___ _/ /__
_\ \/ _ \/ _ `/ __/ '
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12135
**[Test build #70813 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70813/testReport)**
for PR 12135 at commit
[`1b2df22`](https://github.com/apache/spark/commit/1
Github user steveloughran commented on a diff in the pull request:
https://github.com/apache/spark/pull/14731#discussion_r94407115
--- Diff: docs/streaming-programming-guide.md ---
@@ -644,17 +644,90 @@ methods for creating DStreams from files as input
sources.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12135
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70813/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12135
Merged build finished. Test 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 project does not have this feature
e
Github user steveloughran commented on a diff in the pull request:
https://github.com/apache/spark/pull/14731#discussion_r94407382
--- Diff: docs/streaming-programming-guide.md ---
@@ -644,17 +644,90 @@ methods for creating DStreams from files as input
sources.
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16448
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 feature
enabled and wishes so,
1 - 100 of 449 matches
Mail list logo
