-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
[MRG+1] Read-only memmap input data in common tests #10663
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
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
b842978
wip
lesteve 8a4249f
Readd LinearSVR test
lesteve 503b910
Simplify code and tests
lesteve e09c507
create_memmap_backed_data now uses atexit to delete memmap files.
lesteve 03e961e
Fix test on Windows and make atexit.register test more stringent
lesteve 2db25a4
Add whats_new entry
lesteve 2521286
Add whats_new entry about check_estimator changes
lesteve File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Stupid question, but it's not possible to create a memap without physically writing to disk? Creating temp files in multiple
check_estimators_*
functions (for each estimator in scikit-learn) doesn't seem ideal - that certainly wouldn't help test run time. Joblib seems to explicitly forbid this and this also doesn't work withnp.load(..., mmap_mode='r')
but I wonder if there is a workaround. We don't need an actual mmap, just something like behaves like it.Alternatively is it possible to cache the
create_memmap_backed_data
function? the data should be repeated multiple times for different estimators.Mostly a side comment, as this was already the case before this PR..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like there is joblib/joblib#378 , but it's out of the scope for this PR ..