Skip to content

branch-2.1: [fix](Nereids) fix regression framework compare issue and fix code point count #49575 #49740

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
Closed
LiBinfeng-01 wants to merge 4 commits into from
Closed

branch-2.1: [fix](Nereids) fix regression framework compare issue and fix code point count #49575 #49740

LiBinfeng-01 wants to merge 4 commits into from

Conversation

@LiBinfeng-01
Copy link
Contributor

@LiBinfeng-01 LiBinfeng-01 commented Apr 1, 2025

Cherry-picked from #49575

@LiBinfeng-01 LiBinfeng-01 requested a review from yiguolei as a code owner April 1, 2025 10:21
@Thearas
Copy link
Contributor

Thearas commented Apr 1, 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?

@LiBinfeng-01
Copy link
Contributor Author

LiBinfeng-01 commented Apr 1, 2025

run buildall

@morrySnow morrySnow changed the title branch-2.1: [fix](Nereids) fix regression framework compare issue and fix code point count (#49575) branch-2.1: [fix](Nereids) fix regression framework compare issue and fix code point count #49575 Apr 2, 2025
@LiBinfeng-01
Copy link
Contributor Author

LiBinfeng-01 commented Apr 16, 2025

run buildall

1 similar comment
@LiBinfeng-01
Copy link
Contributor Author

LiBinfeng-01 commented Apr 18, 2025

run buildall

@LiBinfeng-01
Copy link
Contributor Author

LiBinfeng-01 commented Apr 18, 2025

run p0

@LiBinfeng-01
Copy link
Contributor Author

LiBinfeng-01 commented Apr 21, 2025

run buildall

@LiBinfeng-01
Copy link
Contributor Author

LiBinfeng-01 commented Apr 24, 2025

run buildall

@LiBinfeng-01
Copy link
Contributor Author

LiBinfeng-01 commented Apr 24, 2025

run feut

@LiBinfeng-01
Copy link
Contributor Author

LiBinfeng-01 commented Apr 24, 2025

run buildall

@LiBinfeng-01
Copy link
Contributor Author

LiBinfeng-01 commented Apr 25, 2025

run p0

@LiBinfeng-01
Copy link
Contributor Author

LiBinfeng-01 commented Apr 25, 2025

run feut

@LiBinfeng-01
Copy link
Contributor Author

LiBinfeng-01 commented Apr 25, 2025

run p0

2 similar comments
@LiBinfeng-01
Copy link
Contributor Author

LiBinfeng-01 commented Apr 27, 2025

run p0

@LiBinfeng-01
Copy link
Contributor Author

LiBinfeng-01 commented Apr 28, 2025

run p0

@github-actions
Copy link
Contributor

github-actions bot commented Oct 26, 2025

We're closing this PR because it hasn't been updated in a while.
This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable.
If you'd like to revive this PR, please reopen it and feel free a maintainer to remove the Stale tag!

@github-actions github-actions bot added the Stale label Oct 26, 2025
@github-actions github-actions bot closed this Nov 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei Awaiting requested review from yiguolei yiguolei is a code owner

Assignees

No one assigned

Labels

Stale

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@LiBinfeng-01 @Thearas