Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

python: always assign best_score after train #890

Merged
merged 1 commit into from
Sep 6, 2017

Conversation

henry0312
Copy link
Contributor

This commit will regain backward compatibility that has been broken
after 015c8ff.
When not using early_stopping, best_score has scores calculated with all trees.

I'm sorry that I overlooked #870 (comment).

This commit will regain backward compatibility that has been broken
after 015c8ff.
@henry0312
Copy link
Contributor Author

@wxchan @StrikerRUS

@guolinke
Copy link
Collaborator

guolinke commented Sep 6, 2017

The travis test on OSX often met time-out error. Can we solve it ?

@henry0312
Copy link
Contributor Author

The travis test on OSX often met time-out error.

This is mostly because Travis has lack of OS X instances... 😢

@guolinke guolinke merged commit de0c174 into microsoft:master Sep 6, 2017
@henry0312 henry0312 deleted the fix_best_score branch September 6, 2017 07:45
@StrikerRUS
Copy link
Collaborator

Yeah, this is sad, but I think we cannot do anything with it (only reduce number of tests on OSX) 😞

@Laurae2
Copy link
Contributor

Laurae2 commented Sep 6, 2017

@guolinke To avoid timeout, can we run several tests in parallel?

@StrikerRUS
Copy link
Collaborator

@guolinke @henry0312 @Laurae2 Can we somehow benefit from caching on OSX?

@guolinke
Copy link
Collaborator

guolinke commented Sep 6, 2017

@StrikerRUS yeah, most time of OSX test are used on package installation.

guolinke pushed a commit that referenced this pull request Sep 6, 2017
@StrikerRUS
Copy link
Collaborator

@guolinke Unfortunately, I have little knowledge of *nix systems, so, probably I'll not be able to do it without your help.

btw, maybe it's better to create a separate issue for Travis speedup?

@StrikerRUS
Copy link
Collaborator

As I understand, we should cache the folder (which one?) with installed packages and at the beginning of build check these packages are already installed.
Like this one, but for Travis:
https://github.com/tunnelvisionlabs/NOpenCL/blob/master/appveyor.yml#L18
https://github.com/tunnelvisionlabs/NOpenCL/blob/master/build/appveyor-install.ps1

@StrikerRUS
Copy link
Collaborator

According to the latest PR, instance just clones git repo and connection to it is lost:
https://travis-ci.org/Microsoft/LightGBM/jobs/272489939
image

I remember cases when instance even cannot be started at all.

So, all our tricks with cache will not be launched...

@guolinke
Copy link
Collaborator

guolinke commented Sep 7, 2017

@StrikerRUS I think it freezes.
@wxchan @henry0312 Is that the bug of OSX ?

@henry0312
Copy link
Contributor Author

I don't know, but it seems a problem of Travis.

@StrikerRUS
Copy link
Collaborator

guolinke pushed a commit that referenced this pull request Oct 9, 2017
This commit will regain backward compatibility that has been broken
after 015c8ff.
guolinke pushed a commit that referenced this pull request Oct 9, 2017
@lock lock bot locked as resolved and limited conversation to collaborators Mar 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants