MAINT: Stabilize MxNE tests #13321
Merged
MAINT: Stabilize MxNE tests #13321
+39
−6
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
|
... and this sort of thing can happen when new tests are added, if those tests (or any underlying functions) make use of the global-state-based |
agramfort
approved these changes
Jul 15, 2025
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.
@Genuster from some testing on SSH I realized it was a Heisenbug -- only showed up on some calls to
pytest mne/inverse_sparse -xk sure_megfor example. I am hoping adding theserandom_state=0s to thesimulate_evokedcalls fixes the bug. I expect them to. Will merge this either way then mergemaininto your branch, and we can continue testing there if needed. But hopefully it just comes back green!