-
Notifications
You must be signed in to change notification settings - Fork 300
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
Unit test failure on Debian Sid #3001
Comments
Do you know what other packages were updated since the last time these tests were run on debian? |
Sorry I cannot say for sure what packages have been updated since the last build. Most probably
By the way satpy 0.52.1-2 was build successfully on 2024-11-04, so less than on month ago. |
The AttributeErrors in Python 3.13 seem like something fsspec needs to fix (but CC @mraspaud and @pnuu just to be sure they see it). The value changes, I wonder if this is from the dtype work that @pnuu did. Would it be possible @avalentino to run the tests for satpy 0.52.1 with the current environment? Actually, regardless, I think the differences in the results are decently within 32-bit floating point precision, right? |
satpy v0.52.1 currently only fails with Python 3.13:
|
For me the tests pass with up-to-date packages from conda-forge with Python 3.12 and Satpy 0.53.0:
|
@pnuu please not that in Debian Sid we still have numpy v1.26 currently |
Ooh, I see! Yeah, with
From my failures I'd set I need to jump to task at work for the rest of the day. Unless someone has PR'd the tolerance changes I think I have time during the evening to do that. |
|
I think @mraspaud (who is on vacation) wanted to add fsspec as a hard requirement for satpy. With that and this request for one of the most recent versions as a limit, that seems pretty strict/difficult for users I would think. Maybe that's just me though. |
Describe the bug
Some of the unit tests fail on Debian Sid (x86_64)
To Reproduce
Expected behavior
All tests pass
Actual results
Python 3.12
Python 3.13
Environment Info:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: