hello-stephen opened a new pull request, #66237:
URL: https://github.com/apache/doris/pull/66237
## What changed
Add a 30-minute deadline to both polling loops in
`cloud_p0.recycler.test_recycler`.
When Recycler or Checker does not advance its finish/success timestamps, the
test
now fails with the relevant timestamps instead of looping until TeamCity's
24-hour build timeout.
## Why
The branch-4.1 Recycler pipeline has repeatedly remained in `test_recycler`
with
no test occurrence until TeamCity terminated the build after 1440 minutes
(for example, builds 204533 and 204268). A normal successful execution of
this
suite in build 203828 took about 11 minutes, so a 30-minute per-phase
deadline
keeps reasonable headroom while turning an infrastructure/service stall into
an
actionable failure.
This does not suppress a Recycler or Checker failure and does not change the
success condition. It only bounds the wait and preserves the last observed
job
timestamps in the error message.
## Validation
- `git diff --check`
- Compared with successful `test_recycler` duration in branch-4.1 build
203828
- Current build 204938 has remained in the same unbounded loop for more than
13 hours with no test occurrence, reproducing the need for this guard
Related: DORIS-27416
--
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]
