Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16905
LGTM merged into 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16905
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75072/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16905
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/16905
**[Test build #75072 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75072/testReport)**
for PR 16905 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16905
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/75070/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16905
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/16905
**[Test build #75070 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75070/testReport)**
for PR 16905 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16905
**[Test build #75072 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75072/testReport)**
for PR 16905 at commit
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16905
Jenkins 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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16905
**[Test build #75070 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/75070/testReport)**
for PR 16905 at commit
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16905
Jenkins, this is 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
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16905
Jenkins 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
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/16905
Hi @squito,
I think jenkins can be triggered again. Last unrelated build - UT issue
looks fixed(https://issues.apache.org/jira/browse/SPARK-19988)
Thanks in advance ;)
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16905
**[Test build #3601 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3601/testReport)**
for PR 16905 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16905
**[Test build #3601 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3601/testReport)**
for PR 16905 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16905
**[Test build #3600 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3600/testReport)**
for PR 16905 at commit
Github user squito commented on the issue:
https://github.com/apache/spark/pull/16905
@shaneknapp I had to trigger jenkins manually via spark-prs. Every once in
a while I encounter a pr for which tests are never triggered via comments. Its
pretty rare, so its not a big deal, but I
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16905
**[Test build #3600 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3600/testReport)**
for PR 16905 at commit
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/16905
Thanks again @kayousterhout and @squito ;)
Jenkins needs to be retriggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user squito commented on the issue:
https://github.com/apache/spark/pull/16905
reopened https://issues.apache.org/jira/browse/SPARK-7420 for the failure
Jenkins, retest this please
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16905
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74629/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16905
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/16905
**[Test build #74629 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74629/testReport)**
for PR 16905 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16905
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74620/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16905
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/16905
**[Test build #74620 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74620/testReport)**
for PR 16905 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16905
**[Test build #74629 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74629/testReport)**
for PR 16905 at commit
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16905
Jenkins retest 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
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/16905
Thanks again @kayousterhout and @squito.
Merge conflict has been fixed and this PR is ready to build on jenkins and
merge (if there is no concern).
---
If your project is set up for
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16905
**[Test build #74620 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74620/testReport)**
for PR 16905 at commit
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16905
Jenkins 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
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/16905
Thanks @kayousterhout and @squito for review this ;)
Last comment is also addressed via last commit: 18657d4.
---
If your project is set up for it, you can reply to this email and
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/16905
Hi @markhamstra, @kayousterhout and @squito
This PR is ready for final review and merge if there is no concern.
All feedbacks are welcome. Thanks in advance ;)
---
If your project
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16905
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/16905
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73299/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16905
**[Test build #73299 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73299/testReport)**
for PR 16905 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16905
retest 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 erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/16905
Thanks @kayousterhout. However, it still looks not triggered.
---
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
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16905
Jenkins this is 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
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/16905
Jenkins, retest 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
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/16905
Many thanks @kayousterhout and @markhamstra.
Also minor scala style issue is fixed with new patch.
---
If your project is set up for it, you can reply to this email and have your
Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/16905
nope, he's not in the admin list. i'll add him now.
---
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
Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/16905
Thanks, Shane & Kay!
---
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
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16905
Awesome thanks Shane!
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16905
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73232/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16905
**[Test build #73232 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73232/testReport)**
for PR 16905 at commit
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16905
@shaneknapp is @markhamstra on the Jenkins whitelist? Wanted to double
check since his attempt to trigger the build above didn't work
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16905
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 kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16905
@erenavsarogullari the reason this was happening on past PRs is that Imran
and I weren't on the Jenkins whitelist (which neither of us realized -- and has
since been fixed). I think Mark is
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16905
**[Test build #73232 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73232/testReport)**
for PR 16905 at commit
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16905
Jenkins 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
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/16905
Thanks @markhamstra.
I encounter the same problem in my every PR and tech-ops team helps to
trigger Jenkins. Problem may be related with Github Jenkins PR Builder plugin.
Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/16905
If Jenkins is listening to me, that should have allowed you to trigger test
for this PR.
test this please
---
If your project is set up for it, you can reply to this email and have
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/16905
Thanks @markhamstra.
I think jenkins needs to be triggered.
---
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
Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/16905
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
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/16905
Hi @markhamstra,
Do you have chance to review this PR and my latest comment?
Thanks in advance ;)
---
If your project is set up for it, you can reply to this email and have your
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/16905
Hi All,
All comments are addressed and this is ready for re-review.
@markhamstra, if it is suitable, i plan to address _removing
SchedulingMode.NONE_ via separated PR. In the
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/16905
Thanks @markhamstra and @srowen for the quick reviews.
I will address them asap by covering the additional patch suggested by Mark.
---
If your project is set up for it, you can reply
Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/16905
@srowen These refactorings of unnecessary vars to vals is something that
we've noted in the discussions of a few other PRs as something that could and
probably should be done in a separate PR
59 matches
Mail list logo
