-
Notifications
You must be signed in to change notification settings - Fork 260
Numerical checks failing in pre-release builds #968
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
This does look like it's likely due to one of your recent PRs @grlee77 . Can you look? Glad you tests the |
yes, I will take a look today |
I cannot reproduce locally with current SciPy master. I suspect this was fixed by the improvements to modes 'nearest' and 'constant' that were merged ~14 hours ago in scipy/scipy#12776. If it occurs again on a newer nightly build, let's revisit the issue |
I don't follow scipy comms closely, so not sure if they're aware that the latest nightly build only pushed 4 wheels? https://anaconda.org/scipy-wheels-nightly/scipy/files |
Example: https://travis-ci.com/github/nipy/nibabel/jobs/434783290
First failures showed up about ~21 hours, so starting around November 12 @ 7pm UTC (2pm EST).
Have a successful build 3 days ago, and scipy has a nightly wheel out 2.5 days ago.
That's my best guess, but I probably won't have time to track down more details until Monday.
@grlee77 @larsoner Would either of you care to have a look?
The text was updated successfully, but these errors were encountered: