-
Couldn't load subscription status.
- Fork 3
Ditch mantid from CI #208
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
Ditch mantid from CI #208
Conversation
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.
I suppose this opens the way to remove conda from the CI (and thus a bunch of env files)? But I suppose this should be done separately, and only after we know if it is worth it (given that we are extracting technique-packages).
| 'PG3_4844_event.zip': 'md5:a644c74f5e740385469b67431b690a3e', | ||
| 'PG3_4866_event.zip': 'md5:5bc49def987f0faeb212a406b92b548e', | ||
| 'PG3_FERNS_d4832_2011_08_24.zip': 'md5:0fef4ed5f61465eaaa3f87a18f5bb80d', |
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.
Interesting, how much of a difference does this make?
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.
For the largest (vana, 4866), a 3x size reduction from 1.5GiB.
Yes, should be done separately, if at all. We may need Mantid for some sub packages it switching away from conda would make that harder in the future. |
Given the struggle in #206 and that I need Scipp 23.08.0 for #203, this PR removes Mantid from the CI builds.
There still are calls to
scn.loadin the loki and imaging modules. But they import Mantid only when called. And they don't seem to get called anywhere.