Github user skanjila commented on the issue:
https://github.com/apache/spark/pull/15848
Yes by all means
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15848
@skanjila Could we close this for 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 this feature
Github user skanjila commented on the issue:
https://github.com/apache/spark/pull/15848
HyukjinKwon I've been out of the country the last 2 weeks, that's why you
don't see updates, I plan to resume work on this next week by making unit
tests in the sql module more reliable, once
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15848
@skanjila We would be able to close this if there are no updates for 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15848
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/15848
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69297/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15848
**[Test build #69297 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69297/consoleFull)**
for PR 15848 at commit
Github user skanjila commented on the issue:
https://github.com/apache/spark/pull/15848
I've changed the underlying trait for LogisticRegressionSuite and
OneVsRestSuite to use local[2], will add in python changes next , want to get
this PR across with this set of changes
---
If
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15848
**[Test build #69297 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69297/consoleFull)**
for PR 15848 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15848
I saw several PRs time to time to run automatic Jenkins tests. So, I
_think_ it is fine to keep this open and push some commits/run some tests to
detect the failure tests if you are proceeding
Github user skanjila commented on the issue:
https://github.com/apache/spark/pull/15848
Sorry I meant Pyspark failures from unit tests , pardon my typos
---
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
Github user skanjila commented on the issue:
https://github.com/apache/spark/pull/15848
@HyujkinKwon I saw at least 3 to 4 failures in unit tests that happened in
Jenkins but not locally (meaning the test succeeded locally). I completely
agree with you about not marking something
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15848
In my personal opinion, I think we should fix here together. Maybe we could
- Run the tests with `--fail-never` flag in the maven in order to list up
the failed tests. If they are few
Github user skanjila commented on the issue:
https://github.com/apache/spark/pull/15848
The plan is to comment out the tests causing Jenkins failures for now, fix
the Python unit tests to work with local[4] and then come back and fix these
other Jenkins failures, make sense?
---
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15848
This is actually what I was worried of initially. So, you mean you are
going to fix the failure tests here in this PR at the end?
---
If your project is set up for it, you can reply to this
Github user skanjila commented on the issue:
https://github.com/apache/spark/pull/15848
Yes the plan is to comment out the failures for now but keep the rest of
the changes, fix the Python unit tests with local[4] and then come back and
fix the rest of the failures, let me know if
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15848
@skanjila are you proceeding with this? if not can you close it for 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15848
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68897/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15848
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/15848
**[Test build #68897 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68897/consoleFull)**
for PR 15848 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15848
**[Test build #68897 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68897/consoleFull)**
for PR 15848 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15848
**[Test build #3422 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3422/consoleFull)**
for PR 15848 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15848
**[Test build #3422 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3422/consoleFull)**
for PR 15848 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15848
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/15848
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68531/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15848
**[Test build #68531 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68531/consoleFull)**
for PR 15848 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15848
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68529/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15848
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/15848
**[Test build #68529 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68529/consoleFull)**
for PR 15848 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15848
**[Test build #68531 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68531/consoleFull)**
for PR 15848 at commit
30 matches
Mail list logo
