Pass a full generation config instead of just sequence length to the runners.

[shoumikhin]

Summary: .

Differential Revision: D83382480

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 3 New Failures, 1 Pending, 3 Unrelated Failures

As of commit 1679d45 with merge base 411578a ():

NEW FAILURES - The following jobs have failed:

• Build Presets / linux (llm, linux.arm64.2xlarge, executorch-ubuntu-22.04-gcc11-aarch64) / build (gh)
• pull / android / run-emulator (gh)
  The process '/usr/bin/sh' failed with exit code 255
• pull / test-samsung-models-linux / linux-job (gh)
  RuntimeError: Command docker exec -t c0db10ce52e0c9601757063e811949d2cb1c1324a1ecd450c3bf4347653755e3 /exec failed with exit code 1

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• pull / test-binary-size-linux-gcc / linux-job (gh) (similar failure)
  ##[error]The operation was canceled.
• pull / unittest-arm-backend-with-no-fvp (test_pytest_models) / linux-job (gh) (detected as infra flaky with no log or failing log classifier)

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / test-setup-linux-gcc / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.

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

[facebook-github-bot]

@shoumikhin has exported this pull request. If you are a Meta employee, you can view the originating diff in D83382480.

[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.

[facebook-github-bot]

@shoumikhin has exported this pull request. If you are a Meta employee, you can view the originating diff in D83382480.

[shoumikhin]

@pytorchbot cherry-pick --onto release/1.0 -c fixnewfeature

[pytorchbot]

Cherry picking #14635

The cherry pick PR is at #14640 and it is recommended to link a fixnewfeature cherry pick PR with an issue. The following tracker issues are updated:

• [v1.0.0] Release Tracker #14288 (comment)

Details for Dev Infra team

Raised by workflow job