-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
PCA singular value non-deterministic test failure on Appveyor #7893
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
I may be missing something but I think the build you are linking to is not a build from master but from the PR #7872 ... This is the latest build from master I can find on AppVeyor and it is all green: |
The build is from a PR that didn't change anything in PCA though. I guess it's a non-deterministic failure? |
which is weird since it's arpack and we set a random state? I'm not entirely sure what the status of our initialization for arpack svds is though, I know there were some recent changes... |
@amueller I want to work on the issue. Could you please guide me as to how can I get started with working on this? |
I just noticed it happened more recently on master: @dalmia this happens on Windows only and not deterministically. Maybe not the best issue if you do not have a Windows machine. |
@amueller Yes, I don't. Thanks for letting me know. |
It happened again in https://ci.appveyor.com/project/sklearn-ci/scikit-learn/build/1.0.14629/job/t8udw2qky46u5ewm (#9108). CI become green after an empty commit. The wrong result in three cases are exactly the same(wrong result:613.0583877392909, right result:613.0583877392893). In order to prevent such confusion, do you agree to change the |
I think it's okay to reduce the precision... but why is the test
non-deterministic?
…On 19 June 2017 at 22:26, Hanmin Qin ***@***.***> wrote:
It happened again in https://ci.appveyor.com/project/sklearn-ci/scikit-
learn/build/1.0.14629/job/t8udw2qky46u5ewm (#9108
<#9108>). CI become
green after an empty commit. The wrong result in three cases are exactly
the same(wrong result:613.0583877392909, right result:613.0583877392893).
In order to prevent such confusion, do you agree to change the decimal
restriction in assert_array_almost_equal from 12 to 6(default value) ? It
seems reasonable to me. @amueller <https:/
8000
/github.com/amueller> @lesteve
<https://github.com/lesteve>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#7893 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEz64uw1wQXVWk4Al6Woh_FkRlQtneUks5sFmkDgaJpZM4K0Hso>
.
|
@jnothman |
See here:
https://ci.appveyor.com/project/sklearn-ci/scikit-learn/build/1.0.10151/job/k042tl5h0hp91iv9
The text was updated successfully, but these errors were encountered: