Repository navigation
[13.x] Fix flaky scheduling test on Windows - #61768
Merged
taylorotwell merged 1 commit intoSep 28, 2026
Merged
Conversation
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fixes an intermittent failure on the Windows jobs.
CommandSchedulingTestswaps Testbench'sartisanscript for a custom one and restores it intearDown(). In the "Background" case the scheduled command runs in a separate process, which can still have that script open whentearDown()runs. Windows won't replace or remove a file another process has open, so the restore fails with "Permission denied", the test errors, and Testbench'sartisanis left as the custom script.