[BugFix] [Spec Decode] Remove LlamaForCausalLMEagle3 to fix CI

[22quinn]

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

"Basic Models Test" has been failing due to some eagle models not named with "eagle-" or "eagle3-" prefix.

This is a short-term fix to make CI green. In the long-term, maybe eagle models should use model_type instead of the name to identify itself, similar to medusa models. But that requires updating config.json in HF repo cc @Liyuhui-12 @LiuXiaoxuanPKU

Test Plan

pytest tests/models/test_initialization.py

Test Result

passed

(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]

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

[DarkLight1337]

The test is still failing, PTAL

[22quinn]

@DarkLight1337 sorry this becomes more involved than I expected, so I removed it to unblock CI.
I got more errors like ValueError: Duplicate layer name: model.layers.1.self_attn.attn. I'll leave it to the original author @lec77 to sort it out.

[hmellor]

Should we comment out the model instead of deleting it? (Makes it easier for future maintainers to know what to add back)

[DarkLight1337]

@22quinn can you address @hmellor 's comment?