Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/19047
+1
---
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/19047
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/19047
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81141/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19047
**[Test build #81141 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81141/testReport)**
for PR 19047 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/19047
LGTM. I'd like to see these daemons start using normal Spark configs like
the applications do, but that's a separate, larger change...
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19047
**[Test build #81141 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81141/testReport)**
for PR 19047 at commit
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/19047
test this please
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19047
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/19047
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81133/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19047
**[Test build #81133 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81133/testReport)**
for PR 19047 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19047
**[Test build #81133 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81133/testReport)**
for PR 19047 at commit
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/19047
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19047
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
13 matches
Mail list logo
