You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 77e0ba4
Browse filesBrowse the repository at this point in the historyBrowse files
Keep bisect log handlers isolated when instance IDs are reused (#439)
Summary:
Pull Request resolved: #439
Creating a BisectLogger with a reused timestamp and object ID can retrieve a previous instance's logger from Python's global logging registry. Its closed handlers then reopen an old log file, mixing output between sessions or raising FileNotFoundError after the old temporary directory has been removed. This caused three setUp errors in GitHub Actions Tests #927: https://github.com/meta-pytorch/tritonparse/actions/runs/35882624122/job/107254643368
Give each BisectLogger its own logging.Logger and detach and close test handlers before removing temporary directories. Add a deterministic regression that forces object ID reuse and covers both retained and deleted previous log directories.
___
Differential Revision: D121418371
fbshipit-source-id: 5f784470861c3cf86c1fb7b51e465364eb1ed500
0 commit comments