Skip to content

Conversation

@DarkLight1337
Copy link
Member

@DarkLight1337 DarkLight1337 commented Oct 22, 2025

Purpose

Also remove workarounds that are only needed in older transformers versions (current minimum is v4.56.0)

Test Plan

Test Result


Essential Elements of an Effective PR Description Checklist
  • The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
  • The test plan, such as providing test command.
  • The test results, such as pasting the results comparison before and after, or e2e results
  • (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
  • (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

Signed-off-by: DarkLight1337 <tlleungac@connect.ust.hk>
@DarkLight1337 DarkLight1337 added the ready ONLY add when PR is ready to merge/full CI is needed label Oct 22, 2025
@mergify
Copy link

mergify bot commented Oct 22, 2025

Documentation preview: https://vllm--27353.org.readthedocs.build/en/27353/

@mergify mergify bot added the documentation Improvements or additions to documentation label Oct 22, 2025
@DarkLight1337 DarkLight1337 enabled auto-merge (squash) October 22, 2025 15:56
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request removes unnecessary flags like min_transformers_version and is_available_online from the test registry, which simplifies the configuration. It also cleans up backward compatibility code for older transformers versions in glm4_1v.py. The changes are generally good, but I found one critical issue where trust_remote_code=True was incorrectly removed for a model, which will likely break CI tests.

@DarkLight1337
Copy link
Member Author

DarkLight1337 commented Oct 22, 2025

@simon-mo if you see any errors related to gated HF repos, can you get access to them? Thanks in advance

Signed-off-by: DarkLight1337 <tlleungac@connect.ust.hk>
Signed-off-by: DarkLight1337 <tlleungac@connect.ust.hk>
@mergify mergify bot added the multi-modality Related to multi-modality (#4194) label Oct 23, 2025
@DarkLight1337
Copy link
Member Author

Thanks @youkaichao for getting access

Signed-off-by: DarkLight1337 <tlleungac@connect.ust.hk>
@DarkLight1337 DarkLight1337 merged commit fe2016d into main Oct 23, 2025
59 checks passed
@DarkLight1337 DarkLight1337 deleted the update-test-registry branch October 23, 2025 14:42
albertoperdomo2 pushed a commit to albertoperdomo2/vllm that referenced this pull request Oct 23, 2025
…27353)

Signed-off-by: DarkLight1337 <tlleungac@connect.ust.hk>
Signed-off-by: Alberto Perdomo <aperdomo@redhat.com>
kingsmad pushed a commit to kingsmad/vllm that referenced this pull request Oct 25, 2025
…27353)

Signed-off-by: DarkLight1337 <tlleungac@connect.ust.hk>
0xrushi pushed a commit to 0xrushi/vllm that referenced this pull request Oct 26, 2025
…27353)

Signed-off-by: DarkLight1337 <tlleungac@connect.ust.hk>
Signed-off-by: 0xrushi <6279035+0xrushi@users.noreply.github.com>
0xrushi pushed a commit to 0xrushi/vllm that referenced this pull request Oct 26, 2025
…27353)

Signed-off-by: DarkLight1337 <tlleungac@connect.ust.hk>
Signed-off-by: 0xrushi <6279035+0xrushi@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation multi-modality Related to multi-modality (#4194) ready ONLY add when PR is ready to merge/full CI is needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants