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
For some reason our test is checking the number of warnings thrown, which will change when any code we are interfacing is deprecated (e.g. loadData in utils). I'll put a PR when I get some time.
maybe two fixes, 1. fix the deprecations, 2. fix the check for the number of warnings unless it is needed. It probably is checking for the extrapolation warnings, so instead of checking the number of warnings, do sthg like checking that warnings are thrown with some message, sthg like that. That makes it robust against a similar failure in the future.
Activity
Sparks29032 commentedon Feb 12, 2026
For some reason our test is checking the number of warnings thrown, which will change when any code we are interfacing is deprecated (e.g. loadData in utils). I'll put a PR when I get some time.
sbillinge commentedon Feb 12, 2026
maybe two fixes, 1. fix the deprecations, 2. fix the check for the number of warnings unless it is needed. It probably is checking for the extrapolation warnings, so instead of checking the number of warnings, do sthg like checking that warnings are thrown with some message, sthg like that. That makes it robust against a similar failure in the future.
Sparks29032 commentedon Feb 24, 2026
Added issue #293 to fix the deprecations