Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/16480
Merging with master.
Not backporting unless people request it since this memory leak is very
minor.
Thanks @sueann !
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16480
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/16480
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70996/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16480
**[Test build #70996 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70996/testReport)**
for PR 16480 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16480
**[Test build #70996 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70996/testReport)**
for PR 16480 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16480
**[Test build #3522 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3522/testReport)**
for PR 16480 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16480
**[Test build #3522 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3522/testReport)**
for PR 16480 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16480
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/16480
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/16480
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70970/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16480
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70972/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16480
**[Test build #70972 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70972/testReport)**
for PR 16480 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16480
**[Test build #70970 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70970/testReport)**
for PR 16480 at commit
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/16480
LGTM pending Jenkins tests
Thanks @sueann !
---
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 jkbradley commented on the issue:
https://github.com/apache/spark/pull/16480
add to whitelist
---
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,
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/16480
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
Github user sueann commented on the issue:
https://github.com/apache/spark/pull/16480
Now the logs show the full class path for the
estimator/evaluator/classifier:
```
INFO Instrumentation: CrossValidator-cv_acb968c4de59-968285285-1:
Github user sueann commented on the issue:
https://github.com/apache/spark/pull/16480
Unit test runs & logs:
* TrainValidationSplit
```
$ build/sbt "test-only
org.apache.spark.ml.tuning.TrainValidationSplitSuiteâ
$ less mllib/target/unit-tests.log
...
Github user sueann commented on the issue:
https://github.com/apache/spark/pull/16480
@jkbradley @thunterdb
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16480
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
20 matches
Mail list logo
