Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18881
I assume this is not needed in other branches since the CVE doesn't affect
Spark?
Merging to master.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18881
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80417/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18881
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/18881
**[Test build #80417 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80417/testReport)**
for PR 18881 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18881
**[Test build #80417 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80417/testReport)**
for PR 18881 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/18881
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 zsxwing commented on the issue:
https://github.com/apache/spark/pull/18881
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/18881
Can you add "Closes #18789" to automate the closing of the other PR?
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18881
cc @zsxwing
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18881
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80384/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18881
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/18881
**[Test build #80384 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80384/testReport)**
for PR 18881 at commit
12 matches
Mail list logo