Skip to content

branch-4.0: [fix](workload policy)query time based be policy not work due to wrong finish_time_ #60456#60535

Merged
yiguolei merged 1 commit intobranch-4.0from
auto-pick-60456-branch-4.0
Feb 6, 2026
Merged

branch-4.0: [fix](workload policy)query time based be policy not work due to wrong finish_time_ #60456#60535
yiguolei merged 1 commit intobranch-4.0from
auto-pick-60456-branch-4.0

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Feb 5, 2026

Cherry-picked from #60456

…g finish_time_ (#60456)

### What problem does this PR solve?

Issue Number: close
[#60454](#60454)

Problem Summary:

### Release note

None

### Check List (For Author)

- Test <!-- At least one of them must be included. -->
    - [x] Regression test
    - [x] Unit Test
    - [x] 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 <!-- Add your reason?  -->

- Behavior changed:
    - [x] No.
    - [ ] Yes. <!-- Explain the behavior change -->

- Does this need documentation?
    - [x] No.
- [ ] Yes. <!-- Add document PR link here. eg:
apache/doris-website#1214 -->

### Check List (For Reviewer who merge this PR)

- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label <!-- Add branch pick label that this PR
should merge into -->
@github-actions github-actions bot requested a review from yiguolei as a code owner February 5, 2026 08:21
@Thearas
Copy link
Contributor

Thearas commented Feb 5, 2026

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?

@dataroaring dataroaring closed this Feb 5, 2026
@dataroaring dataroaring reopened this Feb 5, 2026
@Thearas
Copy link
Contributor

Thearas commented Feb 5, 2026

run buildall

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Feb 5, 2026
@github-actions
Copy link
Contributor Author

github-actions bot commented Feb 5, 2026

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Contributor Author

github-actions bot commented Feb 5, 2026

PR approved by anyone and no changes requested.

@doris-robot
Copy link

BE UT Coverage Report

Increment line coverage 100.00% (10/10) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 53.06% (19117/36028)
Line Coverage 36.21% (178146/491939)
Region Coverage 32.77% (137923/420868)
Branch Coverage 33.69% (59810/177522)

@yiguolei
Copy link
Contributor

yiguolei commented Feb 6, 2026

skip buildall

@yiguolei yiguolei merged commit d1d3045 into branch-4.0 Feb 6, 2026
30 of 33 checks passed
@github-actions github-actions bot deleted the auto-pick-60456-branch-4.0 branch February 6, 2026 03:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

Comments