Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14185
I tried playing a little bit with what this API would look like, and I'm
starting to question my previous idea that exposing the ProcessBuilder is the
way to go here...
The above issue with
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14185
**[Test build #62289 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62289/consoleFull)**
for PR 14185 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14185
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62289/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14185
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/14185
**[Test build #62289 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62289/consoleFull)**
for PR 14185 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14185
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
enabled and wishes so, or if the
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14185
This PR should really be referencing SPARK-14702, which is the older bug.
SPARK-16511 should be closed as a duplicate of it.
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14185
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
