Skip to content

Strip all LOG_* call sites — logging re-tiering baseline#1447

Draft
ChaoZheng109 wants to merge 1 commit into
hw-native-sys:mainfrom
ChaoZheng109:issue-1428-strip-all-logs
Draft

Strip all LOG_* call sites — logging re-tiering baseline#1447
ChaoZheng109 wants to merge 1 commit into
hw-native-sys:mainfrom
ChaoZheng109:issue-1428-strip-all-logs

Conversation

@ChaoZheng109

@ChaoZheng109 ChaoZheng109 commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

Reduce logging footprint (#1428)

Curate LOG_* call sites across the runtime and platform layers: drop
low-signal logs, demote per-item detail to LOG_DEBUG, and keep the
diagnostics that trace program flow or failures.

Net effect vs base (individual call sites; a2a3 / a5 counted separately)

Action Count
Removed 73 (55 LOG_INFO_V0 + 8 LOG_DEBUG + 5 LOG_INFO_V9 + 2 LOG_ERROR + 3 LOG_WARN)
Demoted to LOG_DEBUG 162 (LOG_INFO_V0LOG_DEBUG)
Newly added 0

Curation rules

  • Flow / lifecycle / summary logs kept at INFO; per-item (per-tensor,
    per-arg) detail demoted to LOG_DEBUG; failure paths stay
    LOG_ERROR / LOG_WARN. Loader / device-runner load-path diagnostics
    kept at their original levels.
  • AICPU hot paths (per-task / per-scope dispatch loops) carry no logs
    (codestyle rule 7); DFX collectors keep their buffer-level init/flush
    diagnostics and telemetry counters.
  • STRACE, LOG_RUNTIME_FAILURE and ACL logging left untouched.
  • Log-only support removed with its logs (bookkeeping counters, dump
    scaffolding); out-of-scope strip collateral restored (unused-parameter
    removals, blank-line deletions).

Rebased onto upstream/main; dense dependency diagnostics follow upstream's
debug-only / removed decisions (#1448), completion follows the polling
mechanism (#1435).

@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 04fad2a1-d0a0-4781-ae4c-c63430e7eeda

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@ChaoZheng109
ChaoZheng109 force-pushed the issue-1428-strip-all-logs branch 3 times, most recently from c0a7c39 to e407c3e Compare July 23, 2026 12:09
Trim low-signal LOG_* call sites across the runtime and platform layers,
keeping the diagnostics that trace program flow or failures:

- Flow / lifecycle / summary logs kept at INFO; per-item (per-tensor,
  per-arg) detail demoted to LOG_DEBUG; failure paths stay LOG_ERROR /
  LOG_WARN. Loader / device-runner load-path diagnostics kept at their
  original levels.
- AICPU hot paths (per-task / per-scope dispatch loops) carry no logs
  (codestyle rule 7); DFX collectors keep their buffer-level init/flush
  diagnostics and telemetry counters.
- STRACE, LOG_RUNTIME_FAILURE and ACL logging left untouched.
- Log-only support removed with its logs (bookkeeping counters, dump
  scaffolding); genuine out-of-scope strip collateral restored
  (unused-parameter removals, blank-line deletions).

Rebased onto upstream/main; dense dependency diagnostics follow upstream's
debug-only / removed decisions (hw-native-sys#1448), completion follows the polling
mechanism (hw-native-sys#1435).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant