br: resolve stuck in progress

[Leavrth]

What problem does this PR solve?

Issue Number: close #54140

Problem Summary:
the progress is stuck.

What changed and how does it work?

From the comment in the issue, the progress calls (*NonColorable).Write, which indicates that the stderr is not terminal, so we can check it at first and then redirect to log.

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

[tiprow]

Hi @Leavrth. 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.

[codecov]

Codecov Report

Attention: Patch coverage is 66.66667% with 4 lines in your changes missing coverage. Please review.

Project coverage is 74.9363%. Comparing base (b41ad70) to head (9d2e130).
Report is 148 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #54790        +/-   ##
================================================
+ Coverage   72.8073%   74.9363%   +2.1290%     
================================================
  Files          1558       1597        +39     
  Lines        438397     483043     +44646     
================================================
+ Hits         319185     361975     +42790     
+ Misses        99609      99521        -88     
- Partials      19603      21547      +1944     

Flag	Coverage Δ
integration	49.7118% <66.6666%> (?)

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

Components	Coverage Δ
dumpling	52.9567% <ø> (ø)
parser	∅ <ø> (∅)
br	54.4963% <66.6666%> (+8.5986%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3pointer, YuJuncen

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

The pull request process is described here

Needs approval from an approver in each of these files:

• br/OWNERS [3pointer,YuJuncen]

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]

[LGTM Timeline notifier]

Timeline:

• 2024-08-12 08:39:42.073658664 +0000 UTC m=+170866.777128307: ☑️ agreed by 3pointer.
• 2024-08-12 08:40:58.422495485 +0000 UTC m=+170943.125965127: ☑️ agreed by YuJuncen.

[Leavrth]

/ok-to-test

[tiprow]

@Leavrth: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
tidb_parser_test	9d2e130	link	true	/test tidb_parser_test
fast_test_tiprow	9d2e130	link	true	/test fast_test_tiprow

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.