Re: [PR] [Fix]Fix thread num not reset 0 when fetch failed [doris]

2024-09-18 Thread via GitHub
wangbo merged PR #40855: URL: https://github.com/apache/doris/pull/40855 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@doris.apach

Re: [PR] [Fix]Fix thread num not reset 0 when fetch failed [doris]

2024-09-17 Thread via GitHub
doris-robot commented on PR #40855: URL: https://github.com/apache/doris/pull/40855#issuecomment-2357404304 ClickBench: Total hot run time: 32.02 s ``` machine: 'aliyun_ecs.c7a.8xlarge_32C64G' scripts: https://github.com/apache/doris/tree/master/tools/clickbench-tools

Re: [PR] [Fix]Fix thread num not reset 0 when fetch failed [doris]

2024-09-17 Thread via GitHub
doris-robot commented on PR #40855: URL: https://github.com/apache/doris/pull/40855#issuecomment-2357399318 TPC-DS: Total hot run time: 194191 ms ``` machine: 'aliyun_ecs.c7a.8xlarge_32C64G' scripts: https://github.com/apache/doris/tree/master/tools/tpcds-tools TPC-DS

Re: [PR] [Fix]Fix thread num not reset 0 when fetch failed [doris]

2024-09-17 Thread via GitHub
doris-robot commented on PR #40855: URL: https://github.com/apache/doris/pull/40855#issuecomment-2357388401 TPC-H: Total hot run time: 41176 ms ``` machine: 'aliyun_ecs.c7a.8xlarge_32C64G' scripts: https://github.com/apache/doris/tree/master/tools/tpch-tools Tpch sf100

Re: [PR] [Fix]Fix thread num not reset 0 when fetch failed [doris]

2024-09-14 Thread via GitHub
doris-robot commented on PR #40855: URL: https://github.com/apache/doris/pull/40855#issuecomment-2350887662 TPC-H: Total hot run time: 42835 ms ``` machine: 'aliyun_ecs.c7a.8xlarge_32C64G' scripts: https://github.com/apache/doris/tree/master/tools/tpch-tools Tpch sf100

Re: [PR] [Fix]Fix thread num not reset 0 when fetch failed [doris]

2024-09-14 Thread via GitHub
doris-robot commented on PR #40855: URL: https://github.com/apache/doris/pull/40855#issuecomment-2350883980 TeamCity be ut coverage result: Function Coverage: 36.92% (9474/25663) Line Coverage: 28.28% (77908/275490) Region Coverage: 27.68% (40229/145319) Branch Coverage: 24.2

Re: [PR] [Fix]Fix thread num not reset 0 when fetch failed [doris]

2024-09-13 Thread via GitHub
github-actions[bot] commented on PR #40855: URL: https://github.com/apache/doris/pull/40855#issuecomment-2350877879 PR approved by anyone and no changes requested. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the UR

Re: [PR] [Fix]Fix thread num not reset 0 when fetch failed [doris]

2024-09-13 Thread via GitHub
github-actions[bot] commented on PR #40855: URL: https://github.com/apache/doris/pull/40855#issuecomment-2350877870 PR approved by at least one committer and no changes requested. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHu

Re: [PR] [Fix]Fix thread num not reset 0 when fetch failed [doris]

2024-09-13 Thread via GitHub
wangbo commented on PR #40855: URL: https://github.com/apache/doris/pull/40855#issuecomment-2350874223 run buildall -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsub

Re: [PR] [Fix]Fix thread num not reset 0 when fetch failed [doris]

2024-09-13 Thread via GitHub
doris-robot commented on PR #40855: URL: https://github.com/apache/doris/pull/40855#issuecomment-2350874167 Thank you for your contribution to Apache Doris. Don't know what should be done next? See [How to process your PR](https://cwiki.apache.org/confluence/display/DORIS/How+to+process+y

[PR] [Fix]Fix thread num not reset 0 when fetch failed [doris]

2024-09-13 Thread via GitHub
wangbo opened a new pull request, #40855: URL: https://github.com/apache/doris/pull/40855 ## Proposed changes Fix thread num not reset 0 when fetch failed -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the