Add ignore_eos option to GenerationConfig

[navsud]

Summary: Allow LLM generation to continue until max_new_tokens is reached, even after encountering EOS tokens. This is useful for benchmarking and testing scenarios where complete token generation is desired regardless of natural stopping points.

Reviewed By: kimishpatel

Differential Revision: D91183072

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/16912

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 4 New Failures, 1 Pending

As of commit 01fbe42 with merge base fda6d51 ():

NEW FAILURES - The following jobs have failed:

• pull / test-llama-runner-qnn-linux (fp32, qnn_16a16w, qnn) / linux-job (gh)
  /pytorch/executorch/examples/qualcomm/oss_scripts/llama/qnn_multimodal_runner.cpp:307:7: error: type 'float' cannot be narrowed to 'int32_t' (aka 'int') in initializer list [-Wc++11-narrowing]
• pull / test-llama-runner-qnn-linux (fp32, qnn_8a8w, qnn) / linux-job (gh)
  /pytorch/executorch/examples/qualcomm/oss_scripts/llama/qnn_multimodal_runner.cpp:307:7: error: type 'float' cannot be narrowed to 'int32_t' (aka 'int') in initializer list [-Wc++11-narrowing]
• pull / test-static-llama-qnn-linux (stories_110m) / linux-job (gh)
  /pytorch/executorch/examples/qualcomm/oss_scripts/llama/qnn_llama_runner.cpp:244:7: error: type 'float' cannot be narrowed to 'int32_t' (aka 'int') in initializer list [-Wc++11-narrowing]
• pull / test-static-llama-qnn-linux (stories_260k_bc) / linux-job (gh)
  /pytorch/executorch/examples/qualcomm/oss_scripts/llama/qnn_llama_runner.cpp:244:7: error: type 'float' cannot be narrowed to 'int32_t' (aka 'int') in initializer list [-Wc++11-narrowing]

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-codesync]

@navsud has exported this pull request. If you are a Meta employee, you can view the originating Diff in D91183072.

[kimishpatel]

Review automatically exported from Phabricator review in Meta.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.