[DNM] Debug conda-libmamba-solver + conda-build

[jaimergp]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[jaimergp]

@conda-forge-admin, please rerender

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[jaimergp]

@conda-forge-admin, please rerender

[jaimergp]

This is very interesting 🤔 If I disable the build by adding some mockup build.sh, it does pass? Why would the build process affect the installability of the artifact if the metadata is identical? Trying again with the actual build.

[jaimergp]

Indeed, very interesting 😱

Is conda-build modifying the Solver._index object at some point in certain stages of the post-build analysis? That's the only thing I can think of to explain why it fails with a full build but not with a mocked build.

[mbargull]

Now that's big boy log file we get XD

[mbargull]

It looks like it only fails with

2023-11-22T20:46:38.5859860Z + python -c 'import lsst'
2023-11-22T20:46:38.5860312Z Traceback (most recent call last):
2023-11-22T20:46:38.5868623Z   File "<string>", line 1, in <module>
2023-11-22T20:46:38.5869792Z ModuleNotFoundError: No module named 'lsst'

which is expected due to the exit 0 in build_stackvana.sh.

[mbargull]

If this gives any trouble, you could also do the

python -c "import pathlib, conda.plan; src = pathlib.Path(conda.plan.__file__); text = src.read_text().replace('stack_context_default', 'stack_context'); src.unlink(); src.write_text(text)"

spiel.

[jaimergp]

investigate-cb-key-error also has some extra logging in case we hit a KeyError, and does not raise so the build can proceed without the report. I think the patch does work (you can see the repodata not being re-downloaded). The error is now about import lsst in the tests 🤷

[jaimergp]

Ah, I saw conda/conda-libmamba-solver#393 (comment). Ok, reverting and rerunning.

[jaimergp]

Look, it's passing!