testing: track the llama export times

[mroreo]

Summary:

Based on the initial test times the following times were logged for each of the model export times from the following run

Run IDs:

• 19151256445
• 19052918428
• 19052918424
• 19151256463

Summary

Fixes #10761

Test Plan:

A script is included in this PR to automatically summarize the model export times based on the run ids. As of right now it is a melted table, but this can easily be grouped by different types using pandas groupby if you want to run analyses by the different columns.

python scripts/check_model_export_times.py --github_token="YOUR_GITHUB_ACCESS_TOKEN" --run_id 19151256445 19052918428 19052918424 19151256463

Once the PR is merged, you can then run this by filter date to get all the model export times after a specific date

python scripts/check_model_export_times.py --github_token="YOUR_GITHUB_ACCESS_TOKEN" --created_time="2025-11-01"

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 2 Active SEVs

There are 2 currently active SEVs. If your PR is affected, please view them below:

• Dr CI is temporarily not working due to API fairewall
• Pytorch CI is partially paused for the time being (updated 11/27)

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

[meta-cla]

Hi @mroreo!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

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

[lucylq]

Thanks for putting this up @mroreo! I'll check to see if we have any sort of dashboard to display these metrics.

[mroreo]

@lucylq can you please help re-run the tests

[mroreo]

@lucylq can you help re-run this. I added more configurations and updated the times

[mroreo]

@lucylq could i get a review for this PR?

[lucylq]

Thanks for adding export-time logs, and a script to calculate the aggregate time over multiple GH runs!

[mroreo]

@lucylq how can i get the tests to pass to get this PR merged? New PRs seem to be merging, and then breaking some tests that are unrelated with this PR

[lucylq]

Hi @mroreo sorry for the late response - could you rebase the PR? I will track it and try to merge it. If the test failures are unrelated, we can just click Squash and merge

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.