xgrammar: Add versions 0.2.5, 0.2.5.post1, 0.2.6, 0.2.7 - #2076
Draft
github-actions[bot] wants to merge 5 commits into
Draft
github-actions[bot] wants to merge 5 commits into
github-actions[bot] wants to merge 5 commits into
Conversation
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
The test extra pulls in cohere_melody==0.13.0, a Rust/maturin package with no riscv64 wheel anywhere; its sdist also fails to build (needs a working cargo toolchain), so `pip install <wheel>[test]` fails outright and every cp312/cp313/cp314 job dies before running a single test. Only cp314t passed because CIBW_TEST_SKIP already skips its test phase. Drop CIBW_TEST_EXTRAS in favor of listing the rest of upstream's test extra by hand (minus cohere_melody), and deselect the MELODY-tagged parametrized cases that need it via `-k "not MELODY"`. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011RwtHNpuiuiCk4MstTLu8m
Contributor
Author
|
…5/0.2.5.post1 CI failed all interpreters for both versions with 21 identical AssertionErrors comparing generated grammar strings. Diffing tests/python/test_structural_tag_converter.py between v0.2.5 and v0.2.6 upstream shows the test's expected_grammar fixture was corrected in 0.2.6 (root_0 is missing a whitespace-token pair around a TagDispatch field at 0.2.5/0.2.5.post1's pinned tags) - a deterministic mismatch between the tag's own converter output and its own test fixture, unrelated to riscv64. Deselect just that test for those two versions, mirroring the existing MELODY deselection.
…0.2.5/0.2.5.post1 Same fixture-mismatch class as test_json_schema_style_deepseek_xml_format (a missing pair of whitespace tokens around a TagDispatch field), fixed upstream in v0.2.6. CI on 0.2.5.post1 cp312 failed with this AssertionError. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011RwtHNpuiuiCk4MstTLu8m
test_json_schema_style_qwen_xml_format and test_qwen_parameter_xml_format hit the same expected_grammar fixture bug as the deepseek/minimax cases (missing whitespace tokens around a TagDispatch field), fixed upstream in v0.2.6. Confirmed via diff of tests/python/test_structural_tag_converter.py between the v0.2.5.post1 and v0.2.6 tags, and against the actual CI failure in run 35437211313 (all six 0.2.5/0.2.5.post1 legs). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011RwtHNpuiuiCk4MstTLu8m
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.
Automatically generated by the nightly
check_versions.pyrun.xgrammar v0.2.4 -> v0.2.5, v0.2.5.post1, v0.2.6, v0.2.7
Every
- version:entry added todocs/packages/xgrammar.yamlis built by this PR's ownbuild-xgrammar.ymlrun; merging publishes the wheels.