fix: unexpected print log to stdout by br

[zier-one]

What problem does this PR solve?

Issue Number: close #xxx

Problem Summary:

fix unexpected print log to stdout by br:

before this pr:

[root@br-0 /]# /br log start
Detail BR log in /tmp/br.log.2025-09-01T02.43.10Z
[2025/09/01 02:43:10.714 +00:00] [INFO] [meminfo.go:179] ["use cgroup memory hook because TiDB is in the container"]
Error: Miss parameters task-name: [BR:Common:ErrInvalidArgument]invalid argument

after this pr:

[root@br-0 /]# /br log start
Detail BR log in /var/folders/hg/q6q6z0ls4nn6w8ct5fss2hj40000gn/T/br.log.2025-09-01T12.59.57+0800 
Error: Miss parameters task-name: [BR:Common:ErrInvalidArgument]invalid argument

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign yujuncen for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• br/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

Hi @zier-one. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[pingcap-cla-assistant]

All committers have signed the CLA.

[tiprow]

Hi @zier-one. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[lance6716]

/ok-to-test

[codecov]

Codecov Report

❌ Patch coverage is 63.63636% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 74.5341%. Comparing base (8d5fd73) to head (892d2c7).
⚠️ Report is 5 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #63299        +/-   ##
================================================
+ Coverage   72.7813%   74.5341%   +1.7528%     
================================================
  Files          1832       1848        +16     
  Lines        495715     496473       +758     
================================================
+ Hits         360788     370042      +9254     
+ Misses       112991     103759      -9232     
- Partials      21936      22672       +736     

Flag	Coverage Δ
integration	45.8282% <63.6363%> (?)
unit	72.2544% <0.0000%> (-0.0037%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.8700% <ø> (ø)
parser	∅ <ø> (∅)
br	63.2716% <63.6363%> (+16.7599%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[lance6716]

/retest

[ti-chi-bot]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-linked-issue label, please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456.

_{📖 For more info, you can check the "Contribute Code" section in the development guide.}