mirror of
https://github.com/kuhyx/testsAndMisc.git
synced 2026-11-13 13:30:47 +01:00
Krzysztof kuhy Rudnicki
32de221550
Python tests has been red since ~2026-08-19, failing in "Install dependencies" with pip's resolution-too-deep. That is an install failure, not a test failure -- which means no Python test has actually run in CI for days, on a repo whose Python bar is 100% branch coverage. The CI log names the cause: the resolver backtracks through Brotli 1.0.6 -> 1.0.4 -> 1.0.1 and asgiref 3.8.0 -> 3.7.1 -> 3.6.0, all dragged in by mitmproxy>=10.0, then gives up. Nothing imports it: `git grep mitmproxy` finds it only in a pacman whitelist and a docs file, and check_requirements_sync.py passes without it. Reproduced and fixed locally rather than guessed, on Python 3.11.11 with pip 26.2.1 -- the versions CI uses: pip install --dry-run -r <with mitmproxy> exit 1, resolution-too-deep pip install --dry-run -r <without mitmproxy> exit 0 Left standing: 78 of the 80 requirements are unpinned >= ranges, so this can recur the next time a package with a wide dependency graph is added. CI_GREEN_SKIP=1: this commit IS the fix for the red baseline. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PJrqKERAo5QUeEHWS5Asgp |
||
|---|---|---|
| .. | ||
| lib | ||
| scripts | ||
| .fvmrc | ||
| .pre-commit-config.yaml | ||
| lint_python.sh | ||
| pyproject.toml | ||
| requirements.txt | ||
| run.sh | ||
| shell-coverage-allowlist.txt | ||