Pin Cython below crashing 3.3 release - #1068
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Signed-off-by: Keith Battocchi <kebatt@microsoft.com>
kbattocchi
force-pushed
the
kebatt/fix-ci-build-failures
branch
from
September 28, 2026 17:25
9efb435 to
1de6a38
Compare
kbattocchi
marked this pull request as ready for review
September 28, 2026 19:11
kbattocchi
added this pull request to stack #1070
September 28, 2026 19:44
fverac
approved these changes
Oct 1, 2026
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
2 participants
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.
Since late August, both our nightly and our PR builds have been failing across all environments due to the release of Cython 3.3; for our PR builds, even though we install using
-r lkg.txt, that only controls runtime dependencies not build-time dependencies.The root cause is this Cython issue. The simplest workaround for now is to constrain the build requirement in
pyproject.toml; when we revise how we handle lkg files in our upcoming CI improvements we should also make sure that we keep track of last known good build environments so that we can make our PR builds more reproduceable.