bpo-36511 fix failures in Windows Python arm32 buildbot tests#15181
Conversation
|
The MemoryError might be hiding something else, unless it's because of the string generation. In which case, I'd separate that out from the |
Sorry, something went wrong.
|
The string generation didn't cause a MemoryError. |
Sorry, something went wrong.
|
I'm having trouble backporting to |
Sorry, something went wrong.
(cherry picked from commit ed70a34) Co-authored-by: Paul Monson <paulmon@users.noreply.github.com>
…-15279) * bpo-37531: Fix regrtest timeout for subprocesses (GH-15072) Co-Authored-By: Joannah Nanjekye <joannah.nanjekye@ibm.com> (cherry picked from commit b0c8369) * bpo-36511: Fix failures in Windows ARM32 buildbot (GH-15181) (cherry picked from commit ed70a34) Backport also minor fixes from master (fix typo, remove importlib import).
|
I'm having trouble backporting to |
Sorry, something went wrong.
(cherry picked from commit ed70a34) Co-authored-by: Paul Monson <paulmon@users.noreply.github.com>
@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