support etdump generation in executorch.runtime

[Gasoonjia]

Summary: make et.runtime support etdump generation.

Differential Revision: D80373976

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 9 New Failures

As of commit 75f339b with merge base b02db12 ():

NEW FAILURES - The following jobs have failed:

• Build documentation / build (buck2) / Build doc (gh)
  At least one of the pre-conditions you specified did not hold
• Lint / lintrunner / linux-job (gh)
  >>> Lint for runtime/test/test_runtime.py:
• pull / unittest / linux / linux-job (gh)
  runtime/test/test_runtime.py::RuntimeTest::test_etdump_generation
• pull / unittest / macos / macos-job (gh)
  runtime/test/test_runtime.py::RuntimeTest::test_etdump_generation
• pull / unittest-buck / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 41b0718ca7e07650f852f276cfaa37b022fb878839374a99daabc8c5505ed438 /exec failed with exit code 3
• pull / unittest-buck / macos / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 3
• pull / unittest-editable / linux / linux-job (gh)
  runtime/test/test_runtime.py::RuntimeTest::test_etdump_generation
• pull / unittest-editable / macos / macos-job (gh)
  runtime/test/test_runtime.py::RuntimeTest::test_etdump_generation
• pull / unittest-nxp-neutron / linux-job (gh)
  RuntimeError: Command docker exec -t 2a6d2faed43bf8356de8e28559ff41de2b243b33734591cfd994f490a15e121b /exec failed with exit code 1

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

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D80373976

[mergennachin]

Add unit test

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D80373976

[lucylq]

Lgtm, looks like test failures are old (from 5 days ago), may need to re-export?

Assume the test works locally, if it's disabled because we're unable to set the etdump flag, could you create an issue to track that and add a comment to the test?