Skip to content

[chore](log) remove unused be warning log (#55159)#55295

Merged
yiguolei merged 1 commit intoapache:branch-2.1from
Mryange:branch-2.1-pick-55159
Aug 27, 2025
Merged

[chore](log) remove unused be warning log (#55159)#55295
yiguolei merged 1 commit intoapache:branch-2.1from
Mryange:branch-2.1-pick-55159

Conversation

@Mryange
Copy link
Contributor

@Mryange Mryange commented Aug 26, 2025

Now this log will often be triggered, because we have done the logic that the downstream can end early.
#55159

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

Now this log will often be triggered, because we have done the logic
that the downstream can end early.
@Mryange Mryange requested a review from yiguolei as a code owner August 26, 2025 06:42
@Thearas
Copy link
Contributor

Thearas commented Aug 26, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@Mryange
Copy link
Contributor Author

Mryange commented Aug 26, 2025

run buildall

@hello-stephen
Copy link
Contributor

BE UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 39.15% (10400/26567)
Line Coverage 30.12% (86214/286249)
Region Coverage 27.67% (49784/179914)
Branch Coverage 24.23% (24426/100806)

@yiguolei yiguolei merged commit 71745bf into apache:branch-2.1 Aug 27, 2025
19 of 20 checks passed
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.

4 participants

Comments