Uh oh!
There was an error while loading. Please reload this page.
[fix](exit) stop storage engine in exec_env before exit - #42015
Conversation
doris-robot
commented
Oct 17, 2024
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
dataroaring
commented
Oct 17, 2024
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
dataroaring
commented
Oct 17, 2024
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
doris-robot
commented
Oct 17, 2024
TPC-H: Total hot run time: 41323 ms |
doris-robot
commented
Oct 17, 2024
TPC-DS: Total hot run time: 192686 ms |
doris-robot
commented
Oct 17, 2024
ClickBench: Total hot run time: 33.72 s |
dataroaring
commented
Oct 20, 2024
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
doris-robot
commented
Oct 20, 2024
TeamCity be ut coverage result: |
doris-robot
commented
Oct 20, 2024
TPC-H: Total hot run time: 41073 ms |
doris-robot
commented
Oct 20, 2024
TPC-DS: Total hot run time: 192472 ms |
doris-robot
commented
Oct 20, 2024
ClickBench: Total hot run time: 32.84 s |
Uh oh!
There was an error while loading. Please reload this page.
ae47d03 to
f7a0d00Comparedataroaring
commented
Oct 30, 2024
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
doris-robot
commented
Oct 30, 2024
TPC-H: Total hot run time: 41439 ms |
doris-robot
commented
Oct 30, 2024
TeamCity be ut coverage result: |
doris-robot
commented
Oct 30, 2024
TPC-DS: Total hot run time: 191751 ms |
doris-robot
commented
Oct 30, 2024
ClickBench: Total hot run time: 32.08 s |
PR approved by anyone and no changes requested. |
PR approved by at least one committer and no changes requested. |
) ### What problem does this PR solve? <!-- You need to clearly describe your PR in this part: 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 this function was added. 4. Which codes were refactored and why this part of the code was refactored. 5. Which functions were optimized and what is the difference before and after the optimization. The description of the PR needs to enable reviewers to quickly and clearly understand the logic of the code modification. --> <!-- If there are related issues, please fill in the issue number. - If you want the issue to be closed after the PR is merged, please use "close#12345". Otherwise, use "ref #12345" --> Issue Number: close #xxx <!-- If this PR is followup a preivous PR, for example, fix the bug that introduced by a related PR, link the PR here --> Related PR: #xxx Problem Summary: ### Check List (For Committer) - Test <!-- At least one of them must be included. --> - [ ] Regression test - [ ] Unit Test - [ ] Manual test (add detailed scripts or steps below) - [x] 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 colde files have been changed. - [x] 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 --> - Release note <!-- bugfix, feat, behavior changed need a release note --> <!-- Add one line release note for this PR. --> None ### 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 -->
Proposed changes
Issue Number: close #xxx