-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add a devdeps figure build #448
Conversation
CodSpeed Performance ReportMerging #448 will not alter performanceComparing Summary
|
figure-!devdeps: matplotlib==3.9.1 | ||
figure-!devdeps: mpl-animators==1.1.1 | ||
figure-!devdeps: astropy==6.1.1 | ||
figure-!devdeps: ndcube==2.2.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should these packages not be pinned for figure-devdeps
as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We install all the git versions of them instead, so we can't have both.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yes, I see. Well then won't that (potentially) lead to figure differences as the packages change on git?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah some of the differences could be something irrelevant has changed upstream, or it could be a legitimate API change. Unfortunately there's no way to test the latter without running the risk of the former. fwiw, random hash breakages don't seem to happen that much on astropy/sunpy.
One small question, otherwise looks fine 👍 |
We should test our figures against at least astropy main