Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16298
**[Test build #70215 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70215/testReport)**
for PR 16298 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16298
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16298
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70215/
Test PASSed.
---
Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/16281
I don't think a fork is a good idea, nor do I think there is a reasonable
need for one.
@gatorsmile brought up that the Parquet community refused to build a patch
release: "The problem is
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16281
+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 have this feature
enabled and wishes so, or if the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15018
**[Test build #70216 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70216/testReport)**
for PR 15018 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16281
I don't think we are making a decision at this point to fork ... if we can
really push parquet to make another maintenance bug fix release, that'd be
great.
---
If your project is set up for it,
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16281
I see the point. Then, the forked repository is going for 2.1.1 or 2.1-rc4
ASAP?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/15335
I'm just asking because you guys discussed this and seemed to reach an
agreement, but the PR is still open after a couple of months. I haven't
actually read the code, but can do if you think it
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15018
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
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/15109
@cenyuhai I don't think this is the right fix. You're just undoing part of
what `expireDeadHosts()` does - which means that if you get into this situation
you'll just leak entries in the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15018
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70216/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15018
**[Test build #70216 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70216/testReport)**
for PR 15018 at commit
Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/15335
@vanzin It should be committed if you think it adds enough additional
clarity that it is worth the penalty of making future backporting or other
debugging maintenance a little more difficult.
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16134
Sure, let me submit a PR to backport it to Spark 2.x branches.
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/15335
so is this still good? should it be committed?
---
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 issue:
https://github.com/apache/spark/pull/16298
**[Test build #70215 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70215/testReport)**
for PR 16298 at commit
Github user neggert commented on the issue:
https://github.com/apache/spark/pull/15018
Alright, the PAV algorithm has been completely re-written to follow what's
outlined in "Minimizing Separable Convex Functions Subject to Simple Chain
Constraints". I've tested it with a bunch of
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16298
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
Github user squito commented on the issue:
https://github.com/apache/spark/pull/14079
oops, thanks for letting me know @zsxwing , I just submitted
https://github.com/apache/spark/pull/16298
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user squito opened a pull request:
https://github.com/apache/spark/pull/16298
[SPARK-8425][Scheduler][HOTFIX] fix scala 2.10 compile error
## What changes were proposed in this pull request?
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15018
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15018
**[Test build #70214 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70214/testReport)**
for PR 15018 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15018
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70214/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15018
**[Test build #70214 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70214/testReport)**
for PR 15018 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14512
@mgummelt are you going to update this, file a bug, write a proper summary,
etc? Otherwise should probably close for now.
---
If your project is set up for it, you can reply to this email and have
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/15159
I wonder if there isn't a better way to handle this without having to add
more configs.
e.g., just distribute things if the user asks for it. For example, if
`--py-files` is provided,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16272
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70206/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16272
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16272
**[Test build #70206 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70206/testReport)**
for PR 16272 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16272
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70204/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16272
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16272
**[Test build #70204 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70204/testReport)**
for PR 16272 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16297
---
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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15119#discussion_r92713539
--- Diff:
core/src/test/scala/org/apache/spark/deploy/SparkSubmitUtilsSuite.scala ---
@@ -137,7 +139,9 @@ class SparkSubmitUtilsSuite extends SparkFunSuite
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/16297
Merging to master and 2.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 have this feature
enabled and wishes
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15119#discussion_r92713607
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ---
@@ -175,6 +176,7 @@ private[deploy] class SparkSubmitArguments(args:
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15119#discussion_r92713085
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -445,6 +450,8 @@ object SparkSubmit {
sysProp =
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15119#discussion_r92712931
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -291,8 +292,12 @@ object SparkSubmit {
} else {
Nil
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16287
**[Test build #70211 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70211/testReport)**
for PR 16287 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16287
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16287
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70211/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16272
**[Test build #70213 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70213/testReport)**
for PR 16272 at commit
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/16272#discussion_r92709390
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/StreamingQueryStatusAndProgressSuite.scala
---
@@ -137,12 +174,12 @@ object
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16287
**[Test build #70212 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70212/testReport)**
for PR 16287 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16297
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16297
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70209/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15505
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70196/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16297
**[Test build #70209 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70209/testReport)**
for PR 16297 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16272
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70197/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16287
**[Test build #70211 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70211/testReport)**
for PR 16287 at commit
Github user brkyvz commented on the issue:
https://github.com/apache/spark/pull/16287
@zsxwing @tdas This passed 1,000 times on 2 jenkins tests. The latest test
started tipping over after 1,100 retries
---
If your project is set up for it, you can reply to this email and have your
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/16272#discussion_r92702425
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/StreamingQueryStatusAndProgressSuite.scala
---
@@ -137,12 +146,13 @@ object
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15505
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
enabled
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16251
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16272
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
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15505
**[Test build #70196 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70196/consoleFull)**
for PR 15505 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16272
**[Test build #70197 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70197/consoleFull)**
for PR 16272 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16272
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70201/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16272
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16282
**[Test build #70210 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70210/testReport)**
for PR 16282 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16272
**[Test build #70201 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70201/testReport)**
for PR 16272 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16282
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,
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/16251
Merging to master and 2.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 have this feature
enabled and wishes
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/16297
LGTM, pending tests.
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16281
That is just an example. We definitely need the fix ASAP, right? See[ the
past release
dates](http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.parquet%22%20AND%20a%3A%22parquet%22)
Github user merlintang commented on the issue:
https://github.com/apache/spark/pull/16134
This patch is related to the path #15819 for spark 1.6. In the #15819, I
can add the code from this patch(#16134) now, then we can fix the staging
files issues in the spark 1.6.x.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16251
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70200/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16251
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16251
**[Test build #70200 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70200/testReport)**
for PR 16251 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16293
@cnZach could you close this? This was already implemented in SPARK-8617.
I don't think we need a config option.
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16287
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16287
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70203/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16287
**[Test build #70203 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70203/testReport)**
for PR 16287 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16281
Is the open issue the main purpose of forking?
To resolve it faster than Parquet community?
---
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 issue:
https://github.com/apache/spark/pull/16297
**[Test build #70209 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70209/testReport)**
for PR 16297 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/14079
@squito Scala 2.10 is broken:
https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Compile/job/spark-master-compile-sbt-scala-2.10/3394/console
Could you submit a PR to fix it? Thanks!
---
If
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16134
sounds good to backport into 2.x branches. We can also backport into 1.6 if
it is easy.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16281
There is still an open JIRA: [PARQUET-686 Allow for Unsigned Statistics in
Binary Type](https://issues.apache.org/jira/browse/PARQUET-686)
Because of that bug, we disable the filter push
Github user squito commented on the issue:
https://github.com/apache/spark/pull/14079
thanks @kayousterhout ! appreciate all the time you've spent helping out
on this issue.
merged to master
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16297
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70205/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16297
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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16281
@dongjoon-hyun I am not sure what is your search conditions. In the recent
JIRA, we hit this issue:
- PARQUET-389: Filter predicates should work with missing columns
---
If your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16297
**[Test build #70205 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70205/testReport)**
for PR 16297 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16287
**[Test build #70208 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70208/testReport)**
for PR 16287 at commit
Github user brkyvz commented on the issue:
https://github.com/apache/spark/pull/16287
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,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16287
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16287
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70207/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16287
**[Test build #70207 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70207/testReport)**
for PR 16287 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16287
**[Test build #70207 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70207/testReport)**
for PR 16287 at commit
Github user merlintang commented on the issue:
https://github.com/apache/spark/pull/16134
+1 backport to spark 1.6.x
On Thu, Dec 15, 2016 at 8:14 AM, Xiao Li wrote:
> The staging directory and files will not be removed when users hitting
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16281
For this issue, it was initially PARQUET-363, but all maintenance fix (with
new features) are welcome.
For me, the followings?
- PARQUET-99: Large rows cause unnecessary OOM
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/16290
Ugh - The failure seems to be from `HiveClientSuite` and I dont think its
related to this PR (as pasted below). However I'm refactoring the SparkR test
case, so let me do that and then re-trigger
Github user ash211 commented on the issue:
https://github.com/apache/spark/pull/16281
What are the specific patches to parquet that folks are proposing should be
included in a parquet 1.8.1-spark1 ? Or what would be desired in a
parquet-released 1.8.2 ?
---
If your project is set
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16287
**[Test build #70202 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70202/testReport)**
for PR 16287 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16287
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70202/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16287
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16290
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70199/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16290
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16290
**[Test build #70199 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70199/testReport)**
for PR 16290 at commit
201 - 300 of 470 matches
Mail list logo