-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
"RuntimeWarning: invalid value encountered in true_divide" in tests #19334
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
Comments
If you're starting on this issue, maybe try do one file per PR, or potentially several if the errors are related, not one PR that addresses all of it. |
I think this is confusing. I would say (doesn't matter if the errors are related, because folks can practice having multiple branches):
|
I will join next dev sprint (9th Feb). At first, I will tackle below test.
|
I'm working on |
Working on |
I'll work on |
I'm working on test_iforest_with_uniform_data in sklearn/ensemble/tests/test_iforest.py |
I'm working on |
@mbatoul It helps us, if you could open a PR even if it is on an early stage. |
@lorentzenchr I am still trying to figure out the right way to solve this issue, but I can surely open a PR right now! |
The list is complete. Thank you all for your contributions. |
The following tests throw a
RuntimeWarning
in the current development version
test_sanity_check_pls_regression_constant_column_Y
insklearn/cross_decomposition/tests/test_pls.py
test_iforest_with_uniform_data
insklearn/ensemble/tests/test_iforest.py
test_kernel_gradient
insklearn/gaussian_process/tests/test_kernels.py
test_radius_neighbors_classifier_zero_distance
insklearn/neighbors/tests/test_neighbors.py
test_calibration_multiclass[0-True-isotonic]
insklearn/tests/test_calibration.py
test_estimators[LinearDiscriminantAnalysis()-check_classifiers_one_label]
insklearn/tests/test_common.py
test_random_choice_csc
insklearn/utils/tests/test_random.py
Those warnings are caused by matricial divisions having some element equal to zero in the denominator, either in the test itself or in the function/class called by the test.
The failure can be reproduced locally using
cc @ogrisel, @reshamas
The text was updated successfully, but these errors were encountered: