Add timestamps for pte generation in CI
Open
@mroreo is already working on this.
Since Nov 3, 2025.
good first issue
module: ci
triaged
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
🚀 The feature, motivation and pitch
Regression tracking for aot export times: add some timestamps to indicate how long the llama export took:
https://github.com/pytorch/executorch/blob/d67fb523d9ed6f7ddd09e80782bfe4e369fc99c4/.ci/scripts/test_llama.sh#L268
And fail if the export time is over some threshold. For now, we can set the threshold to be the time it takes to export the longest-running configuration.
The breakdown can look something like this:
- Add timestamps for the export command in CI.
- Observe the time it takes for each llama test in CI runs. Expect different export commands to show different export times.
- Add a fail, if the export time exceeds the largest time observed in (2), with some buffer; I guess we expect some variability with each run.
- Optional add-on: make (3) more fine-grained, and targeted per-command.
Alternatives
No response
Additional context
No response
RFC (Optional)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.