Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The last successful build used Python 3.13 because we select the highest minor version supported by our existing wheels on PyPI. After releasing support for Python 3.14, the profiling tests began using that. The Windows images only ship 3.12 & 3.13 in the tool cache and, since we didn't specify a version, 3.13 was set up. This made uv download its own Python distribution but it selected the one for x86_64 because the team chose to (temporarily) rely on emulation until more wheels in the ecosystem were built natively. We build wheels in a separate step that serves subsequent jobs and the profiling tests download the specific wheel artifact for the given platform rather than downloading everything, hence the error of trying to install an ARM wheel on a different architecture.