Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/13881
Hi @smurching, is this still active?
---
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 jkbradley commented on the issue:
https://github.com/apache/spark/pull/13881
Sorry for the long delay! Whenever you get a chance to update this, it'd
be nice to log this info via the Instrumentation class, rather than logInfo.
---
If your project is set up for it, you
Github user smurching commented on the issue:
https://github.com/apache/spark/pull/13881
Does it make sense to only perform instrumentation-related computations
(i.e. updating the max/min nodes per group) if the instrumentation argument to
RandomForest.run (instr) is not None? This
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13881
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61151/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13881
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/13881
**[Test build #61151 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61151/consoleFull)**
for PR 13881 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13881
**[Test build #61151 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61151/consoleFull)**
for PR 13881 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13881
**[Test build #61150 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61150/consoleFull)**
for PR 13881 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13881
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61150/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13881
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/13881
**[Test build #61150 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61150/consoleFull)**
for PR 13881 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13881
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61144/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13881
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/13881
**[Test build #61144 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61144/consoleFull)**
for PR 13881 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13881
**[Test build #61144 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61144/consoleFull)**
for PR 13881 at commit
Github user mengxr commented on the issue:
https://github.com/apache/spark/pull/13881
ok to test
---
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 the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13881
Can one of the admins verify this patch?
---
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
17 matches
Mail list logo
