rusackas opened a new pull request, #40743: URL: https://github.com/apache/superset/pull/40743
### SUMMARY None of our CI jobs set `timeout-minutes`, so every job inherits GitHub's default of **360 minutes (6 hours)**. A single hung or wedged job — a stuck dev server, a deadlocked Cypress/Playwright process, a stalled network call — keeps a runner busy for up to 6 hours before it's reclaimed. On the matrix workflows (Cypress/Playwright shards, the integration-test databases, the docker build presets) that's a large amount of wasted runner time per incident, and it's silent until someone notices the run hasn't finished. This adds right-sized per-job caps across the compute-heavy workflows, with generous headroom above observed run times (so legitimate slow runs aren't killed — the goal is only to catch hangs): | job(s) | timeout | |---|---| | lead `changes` jobs | 10m | | `setup_matrix` (docker) | 5m | | `pre-commit`, `sharded-jest-tests`, `lint-frontend`, `validate-frontend`, websocket | 20m | | `report-coverage` | 15m | | `test-storybook` | 25m | | `frontend-build`, `cypress-matrix`, `playwright-tests`, `playwright-tests-experimental`, `unit-tests`, `analyze` (CodeQL), `docker-compose-image-tag`, extensions-cli | 30m | | integration (`test-mysql/postgres/sqlite`), presto/hive | 45m | | `docker-build` (multi-platform on push) | 60m | Steady-state cost is unchanged — this only **bounds the worst case** (a hang now dies in minutes, not hours). Purely additive; no other lines touched. ### TESTING INSTRUCTIONS CI-only change. Jobs run as before; confirm each shows its `timeout-minutes` in the run UI. ### ADDITIONAL INFORMATION - [ ] Has associated issue: - [ ] Changes UI - [ ] Includes DB Migration - [ ] Introduces new feature or API - [ ] Removes existing feature or API 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
