You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Numpy-dev failures in master as of 2016-10-18 #5419
Really weird, it looks like some of the problems are due to numbers being formatted differently, possibly because a default format gets set in some remote-data test.
It turns out there is another numpy-dev issue as well (allcose(np.nan, np.nan) no longer returns True), so I think best is to have a PR that fixes this. Working on it...
So for the first look it's seems possible to get e-mails/gitter/slash/etc notifications, but they will be sent out based on the whole travis status and not individual builds.
I'll contact travis to confirm this, and to point to us to a workaround if there is any.
Activity
mhvk commentedon Oct 18, 2016
Really weird, it looks like some of the problems are due to numbers being formatted differently, possibly because a default format gets set in some remote-data test.
mhvk commentedon Oct 18, 2016
Most errors are actually due to a change in numpy-dev, which causes record arrays to be formatted differently: numpy/numpy#8160
[-]Remote data failures in master as of 2016-10-18[/-][+]Numpy-dev failures in master as of 2016-10-18[/+]pllim commentedon Oct 18, 2016
In that case, what is the best way to fix this? Is there a "only run this doctest if numpy is version such and such"?
mhvk commentedon Oct 18, 2016
It turns out there is another numpy-dev issue as well (
allcose(np.nan, np.nan)no longer returnsTrue), so I think best is to have a PR that fixes this. Working on it...mhvk commentedon Oct 18, 2016
@astrofrog - on these "allowed failures" -- would it be possible to autogenerate an e-mail (or issue?) if something is merged in master that fails?
mhvk commentedon Oct 20, 2016
See #5423 for what hopefully will fix the remaining numpy-dev problems...
bsipocz commentedon Oct 23, 2016
@mhvk - I believe it's possible, remind me about it please in a week time (or open an issue somewhere, I can be assigned).
bsipocz commentedon Oct 23, 2016
So for the first look it's seems possible to get e-mails/gitter/slash/etc notifications, but they will be sent out based on the whole travis status and not individual builds.
I'll contact travis to confirm this, and to point to us to a workaround if there is any.
astrofrog commentedon Oct 31, 2016
@mhvk @bsipocz - what about using something like https://gist.github.com/astrofrog/061aed7312da223f76ba38e096981780 as a cron job? (maybe showing only the message when it fails)
astrofrog commentedon Oct 31, 2016
Looks like this can be closed - we should open a new issue if there are other failures. Thanks @mhvk!