Add error logging to scripts/print_exported_headers

[swolchok]

No description provided.

[swolchok]

Stack from ghstack (oldest at bottom):

• ->Add error logging to scripts/print_exported_headers #13686
• Reapply "Add check_for_installed_private_headers_in_cmake_out" (#13485) #13880

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 1 Active SEVs

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

• ROCm MI2xx CI/CD workflows failing due to : download from https://api.github.com/repos/pytorch/pytorch timed out.

❌ 5 New Failures, 1 Unrelated Failure

As of commit 3c75a2d with merge base be65301 ():

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
• Build Presets / windows (pybind) / build (gh)
  Process completed with exit code 1.
• Build Presets / windows (windows) / build (gh)
  Process completed with exit code 1.
• pull / unittest / macos / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1
• pull / unittest-editable / macos / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1

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

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

• pull / unittest-nxp-neutron / linux-job (gh) (trunk failure)
  test_split_group_convolution__applied_by_default

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

[jackzhxng]

Does this need to be imported?

[swolchok]

https://github.com/pytorch/executorch/actions/runs/17416104660/job/49444945169?pr=13686#step:9:20480

stderr: b'[2025-09-02T22:56:22.386+00:00] Build ID: bbf65f19-5632-4134-922b-d34d84471178\nCommand failed: \nError in configured node dependency, dependency chain follows (-> indicates depends on, ^ indicates same configuration as previous):\n root//extension/llm/runner:multimodal_runner_lib (prelude//platforms:default#200212f73efcd57d)\n -> root//extension/llm/runner:text_token_generator (^)\n -> root//extension/llm/tokenizers:headers (^)\n\n\nCaused by:\n 0: looking up unconfigured target node `root//extension/llm/tokenizers:headers`\n 1: Error loading targets in package `root//extension/llm/tokenizers` for target `root//extension/llm/tokenizers:headers`\n 2: package `root//extension/llm/tokenizers:` does not exist\n missing `TARGETS` file (also missing alternatives `TARGETS.v2`, `TARGETS`)\n'

hmm.

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

[meta-cla]

Hi @swolchok!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

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]

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.

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