| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
This PR adjusts a regression test to be resilient to Python interpreter startup latency, so it validates GitPython’s kill_after_timeout behavior rather than intermittently failing due to a too-aggressive deadline. Production code is unchanged.
Changes:
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sorry, something went wrong.
The macOS Python 3.8 Actions job intermittently killed the helper process before it could start and flush its expected output. The 100 ms deadline tested interpreter startup speed rather than GitPython timeout behavior. Keep the timeout regression coverage while allowing one second for process startup. Validation: five focused runs with Python 3.8; Ruff check and format. Co-authored-by: Sebastian Thiel <sebastian.thiel@icloud.com>
| Back | FazBrowse Home | New Git URL |
Tasks
This section is for Byron only. Models continuing this PR must not add, remove, check, uncheck, rename, or reorder checkboxes here.
Everything below this line was generated by Codex.
Created by Codex on behalf of Byron. Byron will review before this is ready to merge.
Reported issue
$issue-full-auto https://github.com/gitpython-developers/GitPython/actions/runs/30193022939/job/89769540615 fails as flake, and only that. Fix it one way or another, exluding it is also fine if there is no alternative.
Change
Increase the timeout regression test deadline from 100 ms to one second so it tests GitPython timeout behavior instead of Python interpreter startup speed. Production code is unchanged.
Validation