-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
test failure in LLE #575
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
Is there some use of a |
The test is using explicit seeding. Maybe the randomness comes from the arpack solver? Or it can be a consequence on the other memory bug in the ball tree implementation. |
There is some randomness in ARPACK, I believe. When calling the fortran routines, one can specify a starting vector - I think that's selected randomly if not supplied. |
I think we should supply a random init vector based on the |
+1 with @ogrisel's solution |
+1 The starting vector can be specified with the |
Should this be closed? |
I think this test can still fail (not sure why). The random_state PR was just a way to get more control in the testing. @mblondel, do you still see this failure? |
Yes, I still see the failure... |
This issue only shows with scipy 0.9 as far as I can tell. |
Should be fixed in da022b8. Can you confirm please? |
Reporting it here (getting similar error during while running nosetests sklearn ) using latest git master (with the patch, verified the change in the source code, but otherwise ready to run examples and learn! thanks for the project Environment: [amilkowski@localhost scikit-learn]$ uname -a FAIL: test_locally_linear.test_lle_simple_gridTraceback (most recent call last):
also dumping scipy version if it helps [amilkowski@localhost scikit-learn]$ sudo yum list scipy Installed Packages |
This is hopefully fixed in #1039 |
@amueller You have a good memory :) I was searching for this ticket to close it. |
I'm (still?) getting a test failure in the LLE module.
The strange thing is that the test passes when test_locally_linear.py is run individually but fails when run from
make test-code
.BTW,
make test
is supposed to run thetest-code
andtest-doc
targets but I noticed that when there is a failure intest-code
,test-doc
is not executed. This means that a failure in a unrelated module to your changes can hide doctest failures.If the test is difficult to fix, we could just skip it, maybe?
The text was updated successfully, but these errors were encountered: