Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17747
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/17747
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79565/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17747
**[Test build #79565 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79565/testReport)**
for PR 17747 at commit
Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/17747
I know, I just have too many open JIRAs to try and manage
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/17747
> How about finalising the review so we can be done with it?
It helps if you address feedback quickly when there is feedback, instead of
taking weeks to do so and leaving a huge window for
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17747
**[Test build #79565 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79565/testReport)**
for PR 17747 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17747
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17747
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79556/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17747
**[Test build #79556 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79556/testReport)**
for PR 17747 at commit
Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/17747
Pushing up a new patched rebased to work with master.
It's getting boring all round for this patch: me having to do a merge,
retest, repush. How about finalising the review so we can
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17747
**[Test build #79556 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79556/testReport)**
for PR 17747 at commit
Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/17747
Mima test failure was about a new method in hist server
```
[info] spark-mllib: found 0 potential binary incompatibilities while
checking against
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17747
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17747
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78120/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17747
**[Test build #78120 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78120/testReport)**
for PR 17747 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17747
**[Test build #78120 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78120/testReport)**
for PR 17747 at commit
Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/17747
I'm going to go with your suggestion and go via the metricServer to get at
the state of counters and gauges; this is is actually better in that it will
verify that all metrics are making
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17747
**[Test build #77059 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77059/testReport)**
for PR 17747 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17747
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/17747
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76113/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17747
**[Test build #76113 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76113/testReport)**
for PR 17747 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17747
**[Test build #76113 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76113/testReport)**
for PR 17747 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17747
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76112/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17747
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/17747
**[Test build #76112 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76112/testReport)**
for PR 17747 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17747
**[Test build #76112 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76112/testReport)**
for PR 17747 at commit
26 matches
Mail list logo
