Skip to content

Adding support for gemma-X-*, llama-X-* naming similar to HF#876

Merged
copybara-service[bot] merged 1 commit intomainfrom
test_843331155
Dec 15, 2025
Merged

Adding support for gemma-X-*, llama-X-* naming similar to HF#876
copybara-service[bot] merged 1 commit intomainfrom
test_843331155

Conversation

@copybara-service
Copy link

Adding support for gemma-X-, llama-X- naming similar to HF

  • current naming did not allow the - after model family for many gemma and llama families. added the support and matched the names as they appear on HF
  • expanded tests to check for model ids as they appear on HF (or substring of what they would be on HF)
  • updated llama3_405b to llama3p1_405b since that is the correct version

- current naming did not allow the `-` after model family for many gemma and llama families. added the support and matched the names as they appear on HF
- expanded tests to check for model ids as they appear on HF (or substring of what they would be on HF)
- updated `llama3_405b` to `llama3p1_405b` since that is the correct version

PiperOrigin-RevId: 844901207
@copybara-service copybara-service bot merged commit 0863146 into main Dec 15, 2025
@copybara-service copybara-service bot deleted the test_843331155 branch December 15, 2025 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant