FrankChen021 opened a new issue, #20473: URL: https://github.com/apache/druid/issues/20473
_This issue was generated automatically by Claude Code (Anthropic's AI coding agent) running a scheduled CI-triage routine on behalf of @FrankChen021. Analysis and suggested fixes are AI-produced; please verify before acting on them._ **Status:** Open: no fix PR **Subject:** `.github/scripts/setup_generate_license.sh` `apt-get update` hang (Static Checks CI, `packaging-check (25) / packaging-check-jdk25`) **Failures:** 1 · **First seen:** 2026-10-01 · **Last seen:** 2026-10-01 ### Root cause `packaging-check.sh` first runs `setup_generate_license.sh`, which calls `sudo apt-get update && sudo apt-get install python3 -y` with no timeout. On 87d36ea342 the runner's `azure.archive.ubuntu.com` mirror was ignored, apt fell back to `archive.ubuntu.com`, and the update stalled after fetching `noble-security InRelease` with no further output until the 60-minute step timeout killed the job. This is a runner/mirror outage, unrelated to the commit (a dependency-classloader change); the same job compiled normally on neighbouring commits. ### Suggested fix Skip the apt step when `python3 -m venv` and `pip3` already work (the `ubuntu-24.04` runner image ships Python 3), or bound it with `timeout 300 sudo apt-get -o Acquire::Retries=3 -o Acquire::http::Timeout=30 update` so a stalled mirror fails fast. ### Occurrences Failed push-triggered master jobs only. The daily triage routine adds one row per new failed job. | Date | Commit | Job | Failure log | Detail | Reported in | |---|---|---|---|---|---| | 2026-10-01 | 87d36ea342 (#20468) | `packaging-check (25) / packaging-check-jdk25` | [job 110455920873](https://github.com/apache/druid/actions/runs/36887937082/job/110455920873) | `apt-get update` in `setup_generate_license.sh` hung after fetching `noble-security InRelease`; step killed at 60-minute timeout | | -- 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]
