Repository navigation
Daily tests failed on Sat Sep 19 2026 #16415
Description
Activity
Hey there! First off, do not worry about these automated daily test failures in typeshed. It is completely normal for upstream type stub changes or daily tool updates to occasionally trip up the CI pipeline, so you are in good company.
When a daily test run like this fails unexpectedly, it usually means that a recent commit introduced a type contradiction, or a newer version of mypy was rolled out in the CI environment that catches a new edge case we need to handle. Since the logs from the specific action run point to a type discrepancy, we typically resolve this by inspecting the stub definition and ensuring our type annotations align cleanly with the latest runtime behavior.
To help track down and test these failures locally before pushing a fix, you can run mypy directly against the affected stub files in your local clone. Here is a quick command setup you can run in your terminal:
Create and activate a fresh virtual environment python -m venv venv source venv/bin/activate Install the exact development dependencies typeshed uses pip install mypy Run mypy specifically on the module stub that failed in the CI logs Replace 'your_module' with the actual path from the traceback mypy typeshed/stubs/your_module
A great habit to get into is running the exact typeshed test suite command locally (usually specified in their CONTRIBUTING.md) right before opening a pull request. It saves you from waiting on remote CI cycles.
If you can share the specific traceback or error log snippet from that action run, we can pinpoint the exact annotation causing the friction right away!
Hope this helps point you in the right direction! Let me know if you run into any issues.
Best,
Usman
Run listed here: https://github.com/python/typeshed/actions/runs/35409129888