[CI/Build] Fix registry tests

[DarkLight1337]

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.

Purpose

• Fix [Misc] Remove redundant config definitions #21891 breaking some registry tests because of missing trust_remote_code
• Fix [Misc] Remove redundant config definitions #21891 breaking Telechat2 model loading
• Temporarily disable HunYuanDenseV1ForCausalLM test because their config.json is missing config classes after a recent commit: https://huggingface.co/tencent/Hunyuan-7B-Instruct-0124/blob/main/config.json

Test Plan

Test Result

(Optional) Documentation Update

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[gemini-code-assist]

Code Review

This pull request addresses several issues related to registry tests and model loading. The changes include adding trust_remote_code=True for multiple models, disabling a test for a model with a missing configuration, and fixing the loading mechanism for the TeleChat2Model. The modifications appear to be correct and necessary for CI stability. I have one suggestion regarding the TeleChat2Model implementation to prevent potential side effects by avoiding in-place modification of the configuration object.

[mgoin]

How did the test registry not run on those previous PRs? We should fix the conditional CI for that job if it didn't trigger

[DarkLight1337]

The registry test did run and pass (except for the known problem with HunYuanDenseV1ForCausalLM)... maybe those configs were inside a local cache in the CI environment so it passed for that PR?

[hmellor]

LGTM!

Let's wait for some CI on this one to be sure

[DarkLight1337]

Tests are passing locally, merging to unblock CI