Skip to content

branch-3.1: [fix](checker) Fix inverted check and test for checker #54403 - #54470

Merged
morrySnow merged 1 commit into
branch-3.1from
auto-pick-54403-branch-3.1
Aug 8, 2025
Merged

branch-3.1: [fix](checker) Fix inverted check and test for checker #54403#54470
morrySnow merged 1 commit into
branch-3.1from
auto-pick-54403-branch-3.1

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Aug 7, 2025

Copy link
Copy Markdown
Contributor

Cherry-picked from #54403

@wyxxxcatYour Name
[fix](checker) Fix inverted check and test for checker (#54403)
40cc00f
related #53876 test:
```
[ RUN ] CheckerTest.normal_check_index_file_v1
[ RUN ] CheckerTest.normal_inverted_check_index_file_v1
[ RUN ] CheckerTest.normal_check_index_file_v2
[ RUN ] CheckerTest.normal_inverted_check_index_file_v2
[ RUN ] CheckerTest.abnormal_check_index_file_v1 (loss key)
[ RUN ] CheckerTest.abnormal_inverted_check_index_file_v1 (loss file)
[ RUN ] CheckerTest.abnormal_inverted_check_index_file_v2 (loss file)
[ RUN ] CheckerTest.abnormal_check_index_file_v2 (loss key)
```
@hello-stephen

hello-stephen commented Aug 7, 2025

Copy link
Copy Markdown
Contributor

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?

@dataroaringdataroaring reopened this Aug 7, 2025
@hello-stephen

hello-stephen commented Aug 7, 2025

Copy link
Copy Markdown
Contributor

run buildall

@doris-robot

doris-robot commented Aug 7, 2025

Copy link
Copy Markdown

Cloud UT Coverage Report

Increment line coverage 68.00% (17/25) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage81.12% (1212/1494)
Line Coverage65.39% (21478/32846)
Region Coverage66.90% (10811/16160)
Branch Coverage56.56% (5698/10074)

@morrySnow
morrySnow merged commit e13fade into branch-3.1Aug 8, 2025
24 checks passed
@github-actions
github-actionsBot deleted the auto-pick-54403-branch-3.1 branch August 8, 2025 02:12
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@morrySnowmorrySnowmorrySnow 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

@hello-stephen@doris-robot@morrySnow@dataroaring@wyxxxcat