bpo-36511 fix failures in Windows Python arm32 buildbot tests#15181
Uh oh!
There was an error while loading. Please reload this page.
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.
@zooba, @zware
win_utils.py: If an exception is thrown during WindowsLoadTracker creation, which is expected on Windows ARM32, then when WindowsLoadTracker.close( ) is called then self.p is not defined. This change ensures that self.p is always initialized.
test_compile.py: test_stack_overflow throws a MemoryException randomly on Windows arm32. I believe this test is running out of memory because the arm32 test hardware only has 1 GB of RAM. What is the best way to fix this? Is handling the MemoryException ok? or does that cover up a real problem?
remoteDeploy.bat: the files in the Parser directory are needed to prevent warnings when running test_asdl_parser.
Please let me know if I should split this into multiple PRs or create new issue(s).
Thanks,
Paul
https://bugs.python.org/issue36511