MRG, MAINT: Cleaner resource use and test tols - #8050
Merged
Conversation
Member
Author
|
Actually I think the Azure error is really numpy/numpy#16913. I'll do a full run here with |
5 tasks
agramfort
approved these changes
Jul 23, 2020
agramfort
left a comment
Member
There was a problem hiding this comment.
LGTM provided CIs are green
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Testing on my Windows machine I found that some of the tolerances were too strict (minor linalg differences when reg=0 in beamformer or for gamma_map). Also I noticed that there were un-freed resources in
test_what.py, which I think is causing this inmasteron Azure:This fixes it by being safer about
fiff_open.