Fix RTD builds by restricting test-nightly platforms #11021
Merged
+6
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this should solve the Pixi issue that's preventing all CIs from passing. I don't know much about it, but I'll merge to keep things moving if that's reasonable; can easily revert
Summary
test-nightlyenvironment tolinux-64andosx-arm64platforms (excludingwin-64)Problem
RTD builds have been failing across all PRs because:
test-nightlyenvironment uses pandas nightly wheels frompypi.anaconda.org/scientific-python-nightly-wheels3.0.0rc0) doesn't currently provide win-64 wheelspixi lockruns, it must solve ALL environments for ALL platforms defined inpixi.tomlpixi lockfresh every buildtest-nightly×win-64combination causes lock file generation to failGitHub Actions CI "hides" this issue by caching
pixi.lock- once generated successfully, subsequent runs skippixi lockentirely.Test plan
🤖 Generated with Claude Code