Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18353
Merged to 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 feature
enabled and wishes so, or
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18353
**[Test build #3847 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3847/testReport)**
for PR 18353 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18353
**[Test build #3847 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3847/testReport)**
for PR 18353 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18353
**[Test build #3846 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3846/testReport)**
for PR 18353 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18353
**[Test build #3846 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3846/testReport)**
for PR 18353 at commit
Github user timvw commented on the issue:
https://github.com/apache/spark/pull/18353
Back on planet earth. Rebased the commits to current spark/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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18353
Ping @timvw
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18353
**[Test build #3829 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3829/testReport)**
for PR 18353 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18353
**[Test build #3829 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3829/testReport)**
for PR 18353 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18353
**[Test build #3825 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3825/testReport)**
for PR 18353 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18353
**[Test build #3825 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3825/testReport)**
for PR 18353 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18353
**[Test build #3824 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3824/testReport)**
for PR 18353 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18353
**[Test build #3824 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3824/testReport)**
for PR 18353 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18353
**[Test build #3820 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3820/testReport)**
for PR 18353 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18353
**[Test build #3820 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3820/testReport)**
for PR 18353 at commit
Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/18353
I thought the historical reason testutils was in main rather than test was
for ease of use by other tests (e.g. python). There's even still a comment in
the code to that effect.
That
16 matches
Mail list logo
