Skip to content

branch-4.1: [fix](regression) Fix docker regression case assertions #65201#65447

Merged
yiguolei merged 1 commit into
branch-4.1from
auto-pick-65201-branch-4.1
Jul 11, 2026
Merged

branch-4.1: [fix](regression) Fix docker regression case assertions #65201#65447
yiguolei merged 1 commit into
branch-4.1from
auto-pick-65201-branch-4.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #65201

### What problem does this PR solve?

Issue Number: None

Related PR: None

Problem Summary: Fix several unstable docker regression cases. LRU
persist now validates restart and dump availability instead of comparing
dump md5 across BE stop/start. TeamCity reporting now resolves the
actual failing Groovy stack frame to avoid reporting failures against
the wrong running suite. Cloud/file cache and compaction cases now avoid
exact segment-count assumptions, poll stale rowset file cache state, and
print rowset, unused_rowsets_count, and file cache diagnostics on
timeout.

### Release note

None

### Check List (For Author)

- Test: Manual test
    - Ran git diff --check for the synchronized regression files.
    - Did not run full docker regression locally.
- Behavior changed: No
- Does this need documentation: No

### What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

### Release note

None

### Check List (For Author)

- Test <!-- At least one of them must be included. -->
    - [x] 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 <!-- 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
- [x] 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 July 10, 2026 06:04
@hello-stephen

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?

@hello-stephen

Copy link
Copy Markdown
Contributor

run buildall

@yiguolei
yiguolei merged commit c79e995 into branch-4.1 Jul 11, 2026
30 of 33 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.

3 participants