-
Notifications
You must be signed in to change notification settings - Fork 92
Add test to ensure binary pipeline maintains threshold after pickling #3027
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
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3027 +/- ##
=======================================
+ Coverage 99.8% 99.8% +0.1%
=======================================
Files 312 312
Lines 30162 30183 +21
=======================================
+ Hits 30073 30094 +21
Misses 89 89
Continue to review full report at Codecov.
|
| ) | ||
|
|
||
|
|
||
| def test_pickled_pipeline_preserves_threshold( |
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.
Can we add some of this logic to test_serialization_protocol or test_load_pickled_pipeline_with_custom_objective instead?
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.
@freddyaboulton both of those tests seem to use cloudpickle, but I wanted to use pickle. Would it be better to edit those tests to include my pickle test, or leave the test as is?
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.
Got it, I see! I wonder if it's possible to merge the tests. We could have a different test fixture than pickled_pipeline_path that uses pickle instead of cloudpickle and move some of the logic from this test in to test_load_pickled_pipeline_with_custom_objective.
Up to you though. If it's better to keep the tests separate, I'm down for it but maybe let's move this test next to test_load_pickled_pipeline_with_custom_objective so that the pickling tests are at least grouped.
freddyaboulton
left a comment
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 good to me @bchen1116 ! Left a non-blocking suggestion for how to organize these tests.
| ) | ||
|
|
||
|
|
||
| def test_pickled_pipeline_preserves_threshold( |
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.
Got it, I see! I wonder if it's possible to merge the tests. We could have a different test fixture than pickled_pipeline_path that uses pickle instead of cloudpickle and move some of the logic from this test in to test_load_pickled_pipeline_with_custom_objective.
Up to you though. If it's better to keep the tests separate, I'm down for it but maybe let's move this test next to test_load_pickled_pipeline_with_custom_objective so that the pickling tests are at least grouped.
…bc_pickle_threshold
Testing thresholds