weiqingy opened a new pull request, #892:
URL: https://github.com/apache/flink-agents/pull/892

   Linked issue: #889
   
   ### Purpose of change
   
   None of the jobs in `ci.yml` set `timeout-minutes`, so a hung test runs 
until GitHub's six-hour per-job ceiling before it is killed. A recent run 
consumed `6h0m16s` on a stalled `it-python` job — the local `llama-server` 
segfaulted mid-run, pytest hung, and the job burned shared Apache runner 
capacity for a result that was knowable in minutes.
   
   This bounds the three jobs that install and exercise a local Ollama server 
(`it-python`, `it-java`, `cross-language`), which are the ones exposed to that 
hang. Each limit is roughly two to three times the job's slowest observed run 
over recent green builds on `main`:
   
   | job | slowest observed (p100, 6 green `main` runs) | `timeout-minutes` |
   |-----|-----|-----|
   | `it-python` | 26.2m | 60 |
   | `cross-language` | 24.8m | 60 |
   | `it-java` | 14.0m | 40 |
   
   The segfault itself is a separate question tracked in #889; this change only 
ensures such a hang fails fast instead of running to the six-hour ceiling.
   
   ### Tests
   
   No test changes. Verified that the workflow YAML still parses and that the 
three `timeout-minutes` keys attach at job level to `python_it_tests`, 
`java_it_tests`, and `cross_language_tests`. The behavior — a job aborting once 
it exceeds its limit — is a GitHub Actions primitive.
   
   ### API
   
   No public API changes.
   
   ### Documentation
   
   - [x] `doc-not-needed`
   


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

Reply via email to