github-actions[bot] commented on code in PR #67947:
URL: https://github.com/apache/doris/pull/67947#discussion_r4004238750
##########
regression-test/suites/statistics/test_analyze_mv.groovy:
##########
@@ -686,15 +686,15 @@ suite("test_analyze_mv") {
sql """insert into mvTestDup values (1, 2, 3, 4, 5), (1, 2, 3, 4, 5), (10,
20, 30, 40, 50), (10, 20, 30, 40, 50), (100, 200, 300, 400, 500), (1001, 2001,
3001, 4001, 5001);"""
connect(context.config.jdbcUser, context.config.jdbcPassword, url) {
sql """use test_analyze_mv"""
- for (int i = 0; i < 10; i++) {
+ for (int i = 0; i < 120; i++) {
Review Comment:
The polling window still ends at the exact boundary of one normal refresh
delay and one allowed backend RPC. If the insert lands just after a
`TabletStatMgr` cycle, the daemon can wait almost 60 seconds and a successful
`getTabletStat()` can then take just under `backend_rpc_timeout_ms` (60
seconds); this loop's last query runs around 119 seconds, after which it sleeps
and asserts the stale row without querying again. That leaves a valid timing
where this stabilization still flakes. Please use the suite's existing
120-by-five-second row-count budget (or equivalent slack) and avoid sleeping
after the final observation without a re-query.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
