urllib3 ci: putting a time limit on jobs (Fix)

The Fix

pip install urllib3==1.26.7

Based on closed urllib3/urllib3 issue #2341 · PR/commit linked

Production note: Most teams hit this during upgrades or environment changes. Roll out with a canary and smoke critical endpoints (health, OpenAPI/docs) before 100%.

Open PR/Commit

@@ -9,6 +9,7 @@ defaults:
   package:
     runs-on: ubuntu-latest
+    timeout-minutes: 10
 
     steps:

fix.md

Option A — Upgrade to fixed release\npip install urllib3==1.26.7\nWhen NOT to use: This fix should not be used if longer job execution times are necessary.\n\n

Why This Fix Works in Production

Trigger: Some CI runs got stuck and only failed after 6 hours, example: https://github.com/urllib3/urllib3/actions/runs/1064318368
Mechanism: CI jobs were running excessively long without a timeout limit
Why the fix works: Sets a lower timeout for CI jobs to prevent them from running excessively long. (first fixed release: 1.26.7).

Production impact:

If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.

Why This Breaks in Prod

CI jobs were running excessively long without a timeout limit
Production symptom (often without a traceback): Some CI runs got stuck and only failed after 6 hours, example: https://github.com/urllib3/urllib3/actions/runs/1064318368

Proof / Evidence

GitHub issue: #2341
Fix PR: https://github.com/urllib3/urllib3/pull/2343
First fixed release: 1.26.7
Reproduced locally: No (not executed)
Last verified: 2026-02-09
Confidence: 0.95
Did this fix it?: Yes (upstream fix exists)
Own content ratio: 0.71

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

Jump to Sources Open on GitHub

“Some CI runs got stuck and only failed after 6 hours, example: https://github.com/urllib3/urllib3/actions/runs/1064318368 Even though it's free it's seems like a big waste, so I propose we set a time limit on all jobs. I think 10 minutes is”

Issue thread · issue description · source

Failure Signature (Search String)

Some CI runs got stuck and only failed after 6 hours, example: https://github.com/urllib3/urllib3/actions/runs/1064318368
Even though it's free it's seems like a big waste, so I propose we set a time limit on all jobs. I think 10 minutes is reasonable (from a glance it seems most jobs take 1m-2m).

Copy-friendly signature

signature.txt

Failure Signature
-----------------
Some CI runs got stuck and only failed after 6 hours, example: https://github.com/urllib3/urllib3/actions/runs/1064318368
Even though it's free it's seems like a big waste, so I propose we set a time limit on all jobs. I think 10 minutes is reasonable (from a glance it seems most jobs take 1m-2m). The `timeout-minutes: ...` directive does this.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
Some CI runs got stuck and only failed after 6 hours, example: https://github.com/urllib3/urllib3/actions/runs/1064318368
Even though it's free it's seems like a big waste, so I propose we set a time limit on all jobs. I think 10 minutes is reasonable (from a glance it seems most jobs take 1m-2m). The `timeout-minutes: ...` directive does this.

What Broke

Some CI runs got stuck and only failed after 6 hours, wasting resources.

Why It Broke

CI jobs were running excessively long without a timeout limit

Fix Options (Details)

Option A — Upgrade to fixed release Safe default (recommended)

pip install urllib3==1.26.7

When NOT to use: This fix should not be used if longer job execution times are necessary.

Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.

Fix reference: https://github.com/urllib3/urllib3/pull/2343

First fixed release: 1.26.7

Last verified: 2026-02-09. Validate in your environment.

When NOT to Use This Fix

This fix should not be used if longer job execution times are necessary.

Did This Fix Work in Your Case?

Quick signal helps us prioritize which fixes to verify and improve.

Prevention

Add a CI check that diffs key outputs after upgrades (OpenAPI schema snapshots, JSON payload shapes, CLI output).
Upgrade behind a canary and run integration tests against the canary before 100% rollout.
Make timeouts explicit and test them (unit + integration) to avoid silent behavior changes.
Instrument retries (attempt count + reason) and alert on spikes to catch dependency slowdowns.

Version Compatibility Table

Version	Status
1.26.7	Fixed

Related Issues

No related fixes found.

Cluster: urllib3:configuration-error urllib3 hub urllib3 best practices All hubs All clusters

Related clusters: Data consistency SSL handshake Other

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.