Add event tracing and ETDumps to executor_runner

[benkli01]

• Enabled via EXECUTORCH_ENABLE_EVENT_TRACER
• Add flag 'etdump_path' to specify the file path for the ETDump file
• Add flag 'num_executions' for number of iterations to run
• Create and pass event tracer 'ETDumpGen'
• Save ETDump to disk
• Update docs to reflect the changes

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 2 New Failures

As of commit 50b711e with merge base 6c69ebd ():

NEW FAILURES - The following jobs have failed:

• Check Labels / Check labels (gh)
  RuntimeError: Error checking labels: PR does not have required labels
• pull / test-export-llava-linux / linux-job (gh)
  RuntimeError: operator torchvision::nms does not exist

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

[pytorch-bot]

Didn't find following labels among repository labels: partner:arm

[benkli01]

@pytorchbot label 'partner: arm'

[benkli01]

The failing test looks unrelated to my changes.

[digantdesai]

Looks good to me. Left some comments. I assume you tried running this with both portable and XNNPACK, with and without this flag and it works OK?

Do you want to add a test with this flag enabled just so we can catch any build issues in this part of the logic?

[facebook-github-bot]

@digantdesai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[benkli01]

Thanks for the review @digantdesai ! I pushed a patch with some changes.

I assume you tried running this with both portable and XNNPACK, with and without this flag and it works OK?

Yes, I didn't see any problems.

Do you want to add a test with this flag enabled just so we can catch any build issues in this part of the logic?

Sure. Where would you add this test? I haven't found an obvious place.

[facebook-github-bot]

@digantdesai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[GregoryComer]

Hey @benkli01, I ended up needing to back out this change due to it breaking the test-llama-runner-qnn-linux job (see https://github.com/pytorch/executorch/actions/runs/10398365231/job/28795542762). I apologize for the inconvenience, it didn't get caught on the PR. I'm happy to help re-land this, as this is a change that we want to keep. Thanks.

[digantdesai]

cc @cccclai

[github-actions]

This PR needs a release notes: label

If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

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

[benkli01]

Re-opened with #5027 as this change was reverted.