Open javierggt opened 7 months ago
Probably unrelated, but I figured we're just building for python 3.11.8 now.
yes, but that should have no effect, actually.
Did this get fixed, fix itself, or is it still broken (for some packages or ?)?
should be broken. We built the packages in 2024.1 before this.
It had just looked to me, for example, that the recent non-fsds packages reported "success" for builds on all platforms https://github.com/sot/acdc/actions/runs/8473025950/job/23216438511
If the issue is that windows builds are still broken for xija, ska_numpy, and other c or c++ conda packages that's smaller scope. Or maybe I'm just misunderstanding.
yes, this affects only packages that actually use libraries. I don't know which ones it affects
Looks like it doesn't impact xija.
If the current strategy is to just wait for the next failure and then work to fix it, this doesn't need an issue.
This workflow failed, and it is basically the same that was used to build the current package in test: https://github.com/sot/test-actions/actions/runs/8175012785
This is how I triggered it:
The error: