Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18211
If I read correctly, you're changing the wire protocol, aren't you?
That's bad. It means a new Spark cannot talk to an old shuffle service. We
can't force people to upgrade the shuffle servic
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18211
**[Test build #77790 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77790/testReport)**
for PR 18211 at commit
[`31070fc`](https://github.com/apache/spark/commit/31
Github user jinxing64 commented on the issue:
https://github.com/apache/spark/pull/18211
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 and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18211
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/18211
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/8/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18211
**[Test build #8 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/8/testReport)**
for PR 18211 at commit
[`31070fc`](https://github.com/apache/spark/commit/3
