Commit b8f98c7
Bump CI timeout to 600s + add telemetry opt-out env vars (ar-r82f.16)
Pragmatic ship for the lingering interpreter-shutdown hang. Cycle 3
confirmed pytest itself completes (no traceback in the killed runs),
but the Python interpreter hangs ~5min on exit, triggering the outer
timeout 300s and producing exit 124 / FAILURE despite a clean test run.
Two-part fix:
1. Bump outer `timeout` from 300s to 600s on both pytest steps. Even
if the interpreter still sits in atexit handlers for several
minutes, it has room to complete naturally instead of being killed.
2. Add belt-and-suspenders telemetry opt-out env vars on both steps,
targeting the dependencies most likely to be registering atexit
network calls:
- CREWAI_DISABLE_TELEMETRY / CREWAI_DISABLE_TRACKING: the other
crewai-recognized opt-out names (CREWAI_TELEMETRY_OPT_OUT alone
turned out to be a documented-but-unrecognized no-op).
- ANONYMIZED_TELEMETRY: chromadb's opt-out switch.
- POSTHOG_DISABLED: posthog (used by chromadb/crewai) opt-out.
Any one of these may shorten the hang; together with the 600s budget
the workflow should report SUCCESS on clean runs while still surfacing
real pytest failures (cycle 1 verified this works in 8.47s).
bead: ar-r82f.16
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>1 parent 038bf21 commit b8f98c7
1 file changed
Lines changed: 10 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
38 | 38 | | |
39 | 39 | | |
40 | 40 | | |
| 41 | + | |
| 42 | + | |
41 | 43 | | |
42 | 44 | | |
43 | | - | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
44 | 48 | | |
45 | 49 | | |
46 | 50 | | |
47 | 51 | | |
48 | 52 | | |
| 53 | + | |
| 54 | + | |
49 | 55 | | |
50 | 56 | | |
51 | | - | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
0 commit comments