Make test_ridge_regression_dtype_stability less random #13816
Merged
Conversation
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
|
Note that this test in one of the 2 tests that currently fail on the travis CRON job: https://travis-ci.org/scikit-learn/scikit-learn/builds/529275776 |
NicolasHug
approved these changes
May 7, 2019
jnothman
reviewed
May 8, 2019
| @@ -998,16 +998,18 @@ def test_dtype_match_cholesky(): | |||
|
|
|||
| @pytest.mark.parametrize( | |||
| 'solver', ['svd', 'cholesky', 'lsqr', 'sparse_cg', 'sag', 'saga']) | |||
| def test_ridge_regression_dtype_stability(solver): | |||
| random_state = np.random.RandomState(0) | |||
| @pytest.mark.parametrize('seed', range(1)) | |||
There was a problem hiding this comment.
It's meant to make it easy to edit this test to run on 100s of different seeds. We probably need a more generic way to achieve this with a fixture.
agramfort
approved these changes
May 8, 2019
Merged
jnothman
pushed a commit
to jnothman/scikit-learn
that referenced
this pull request
May 8, 2019
|
We could have a random_seed pytest.fixture that is different on different
ci?
|
koenvandevelde
pushed a commit
to koenvandevelde/scikit-learn
that referenced
this pull request
Jul 12, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As reported in #13350 (comment) a new test introduced in #13302 tend to fail randomly when changing the seed (also one of the rng used internally was a module level singleton which caused the tests to be dependent on other tests).
I changed the test criterion to work with a wide variety of random problems (I tried all
seed in range(100)).I have observed a few catastrophic failures with
sparse_cginfloat32: some coefs could have very large magnitude. Maybe we should disable float32 bit data forsparse_cg.