Fix logging.info not appearing

[jackzhxng]

Summary

Logs at the info level were not appearing for export_llama, omitting useful logs for intermediate export states with --verbose. This also fixes for when a debugger is being used.

Test plan

Ran export_llama instructions from README

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 3 New Failures

As of commit a9652e8 with merge base 1308d4d ():

NEW FAILURES - The following jobs have failed:

• Lint / lintrunner / linux-job (gh)
  >>> Lint for backends/cadence/aot/export_example.py:
• pull / test-eval_llama-wikitext-linux / linux-job (gh)
  RuntimeError: Command docker exec -t e8ad77f6db4bd2c8b5f985a88527cea49557a2047f5bca924745037739183118 /exec failed with exit code 1
• pull / test-llava-runner-linux / linux-job (gh)
  test_llava_export

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

[lucylq]

lgtm

as a note, seems like this is overriding the warning log in xnnpack partitioner:
https://github.com/pytorch/executorch/blob/main/backends/xnnpack/partition/xnnpack_partitioner.py#L26

could potentially move that to info?

[jackzhxng]

Yeah it's overriding the earliest logging levels which is set somewhere in the export_llama dependencies. Maybe one of the recursive module imports recently had a logging level initialized to WARNING or lower.

Since global logging level can only be configured once, should we remove the logging.basicConfig calls in modules such as https://github.com/pytorch/executorch/blob/main/extension/llm/export/builder.py#L46? If they want to specify a level they should probably be using named loggers cc @dbort