Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16163
Alright let's try this ... Merging in 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
Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/16163
@srowen Thanks. I sent this one because the `consoleFull` page frequently
freezes my browser these days, not mentioning viewing Jenkins build results via
mobile phone...
---
If your project is
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16163
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/16163
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69703/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16163
**[Test build #69703 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69703/testReport)**
for PR 16163 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16163
It might not be exactly the same thing, but I remember we changed something
like this in the opposite way -- to link straight to the full output since
typically you need that to debug a failure, and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16163
**[Test build #69703 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69703/testReport)**
for PR 16163 at commit
