Skip to content

[cherry-pick](branch-21) pick (#50913) #51072

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
yiguolei merged 1 commit into from
May 22, 2025
Merged

[cherry-pick](branch-21) pick (#50913) #51072

yiguolei merged 1 commit into from
May 22, 2025

Conversation

@zhangstar333
Copy link
Contributor

@zhangstar333 zhangstar333 commented May 20, 2025 •
edited
Loading

What problem does this PR solve?

Problem Summary:
pick from master (#50913)

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

@zhangstar333 zhangstar333 requested a review from yiguolei as a code owner May 20, 2025 07:22
@zhangstar333
Copy link
Contributor Author

zhangstar333 commented May 20, 2025

run buildall

@Thearas
Copy link
Contributor

Thearas commented May 20, 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?

@hello-stephen
Copy link
Contributor

hello-stephen commented May 20, 2025

BE UT Coverage Report

Increment line coverage 0.00% (0/86) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 39.03% (10322/26449)
Line Coverage 30.02% (85721/285512)
Region Coverage 28.70% (44237/154133)
Branch Coverage 25.42% (22629/89020)

@hello-stephen
Copy link
Contributor

hello-stephen commented May 20, 2025

BE Regression && UT Coverage Report

Increment line coverage 0.00% (0/86) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 46.34% (12073/26054)
Line Coverage 36.98% (104922/283708)
Region Coverage 33.87% (60778/179445)
Branch Coverage 29.20% (29397/100676)

@hello-stephen
Copy link
Contributor

hello-stephen commented May 21, 2025

BE Regression && UT Coverage Report

Increment line coverage 0.00% (0/86) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 46.07% (12003/26054)
Line Coverage 36.75% (104261/283708)
Region Coverage 33.67% (60419/179445)
Branch Coverage 29.07% (29262/100676)

@zhangstar333
Copy link
Contributor Author

zhangstar333 commented May 21, 2025

run buildall

@hello-stephen
Copy link
Contributor

hello-stephen commented May 21, 2025

BE UT Coverage Report

Increment line coverage 1.14% (1/88) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 39.02% (10323/26456)
Line Coverage 30.03% (85774/285647)
Region Coverage 28.69% (44250/154254)
Branch Coverage 25.41% (22642/89120)

@hello-stephen
Copy link
Contributor

hello-stephen commented May 21, 2025

BE Regression && UT Coverage Report

Increment line coverage 1.14% (1/88) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 46.33% (12075/26061)
Line Coverage 37.00% (105020/283843)
Region Coverage 33.86% (60805/179576)
Branch Coverage 29.19% (29417/100780)

@zhangstar333 zhangstar333 changed the title [cherry-pick](branch-21) pick (#50913) (#49212) [cherry-pick](branch-21) pick (#50913) May 21, 2025
@zhangstar333
Copy link
Contributor Author

zhangstar333 commented May 21, 2025

run buildall

@doris-robot
Copy link

doris-robot commented May 21, 2025

BE UT Coverage Report

Increment line coverage 0.00% (0/9) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 39.01% (10321/26456)
Line Coverage 30.02% (85748/285636)
Region Coverage 28.67% (44230/154250)
Branch Coverage 25.39% (22631/89116)

@hello-stephen
Copy link
Contributor

hello-stephen commented May 21, 2025

BE Regression && UT Coverage Report

Increment line coverage 100.00% (9/9) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 74.60% (19441/26061)
Line Coverage 69.35% (196832/283832)
Region Coverage 66.83% (120002/179572)
Branch Coverage 59.94% (60402/100776)

@yiguolei yiguolei merged commit fbad523 into apache:branch-2.1 May 22, 2025
21 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei yiguolei approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@zhangstar333 @Thearas @hello-stephen @doris-robot @yiguolei