Skip to content
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

Builds on osx & win failing #147

Closed
h-vetinari opened this issue Jun 27, 2023 · 3 comments
Closed

Builds on osx & win failing #147

h-vetinari opened this issue Jun 27, 2023 · 3 comments

Comments

@h-vetinari
Copy link
Member

h-vetinari commented Jun 27, 2023

It appears there's some wide-spread breakage in osx & windows builds happening since about 20min; happens on every PR I've looked at that started since then. Failure looks like:

  File "/Users/runner/miniforge3/lib/python3.10/site-packages/conda_index/index/__init__.py", line 347, in _get_resolve_object
    sd._process_raw_repodata(repodata_copy)  # type: ignore
TypeError: SubdirData._process_raw_repodata() missing 1 required positional argument: 'state'

This happens before the actual build step of a given feedstock even runs, during the "Attempting to finalize metadata for " phase.

While it's pure speculation, I have a suspicion that it might be related to conda-forge/miniforge#466 (at least, no other relevant packages that I checked seemed to have been updated recently).

CC @conda-forge/core

@jakirkham
Copy link
Member

Interesting have not noticed this on macOS builds I've been working on (for example). Not saying there are not issues, but perhaps the scope is more limited

Could you please share some examples where this occurs?

@h-vetinari
Copy link
Member Author

From what I can tell, Isuru marked the problematic release as a pre-release, so presumably it shouldn't get pulled into builds anymore. I first saw this in conda-forge/opencv-feedstock#363, but when I checked the overall pipelines tab for conda-forge, the first 5 builds I checked were all affected.

I restarted the builds in opencv and it seems this has fixed the fallout.

@h-vetinari
Copy link
Member Author

For me it's fine to close this issue. I don't doubt the breakage will be investigated before the trigger is pulled a second time. Thanks for the quick response everyone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants