shuke987 opened a new pull request, #67844:
URL: https://github.com/apache/doris/pull/67844

   ### What problem does this PR solve?
   
   Problem Summary:
   
   The automated review of #67687 hit the 90-minute step timeout while 
finishing its report ([failed 
run](https://github.com/apache/doris/actions/runs/34488778375/job/102909763020));
 its [formal 
review](https://github.com/apache/doris/pull/67687#pullrequestreview-5169396336)
 was submitted about 23 seconds later.
   
   Increase the review step timeout from 90 to 120 minutes. Raise the job 
timeout from 208 to 238 minutes and update the budget comment, preserving 8 
minutes for auth synchronization and 12 minutes for runner setup and post-job 
cleanup.
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test:
     - [x] Unit Test: all 18 existing `test_review_auth_quarantine.py` tests 
passed against the modified workflow using fake OSS, Codex, and GitHub services.
     - [x] Manual test: parsed the YAML and verified the 120-minute review 
limit, 218-minute pre-finalization budget, 8-minute auth sync, and 12-minute 
reserve within the 238-minute job limit. Confirmed no other parsed workflow 
changes; patch whitespace check passed.
   - Behavior changed:
     - [x] Yes. Automated reviews may run for up to 120 minutes.
   - Does this need documentation?
     - [x] No. The workflow budget comment is updated.
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label
   


-- 
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]

Reply via email to