From c7e9b7077042f2341c594998ca587165134af010 Mon Sep 17 00:00:00 2001 From: Matt Page Date: Thu, 6 Mar 2025 08:47:10 -0800 Subject: [PATCH] Fix `test_list.ListTest.test_no_memory` under trace refs build Memory allocation ends up failing in _PyRefchainTrace(), which produces different output. Assert that we don't segfault, which is the thing we want to test and is less brittle than checking output. --- Lib/test/test_list.py | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/Lib/test/test_list.py b/Lib/test/test_list.py index 2a34fd04f35059..725e07f3ad023f 100644 --- a/Lib/test/test_list.py +++ b/Lib/test/test_list.py @@ -1,3 +1,4 @@ +import signal import sys import textwrap from test import list_tests, support @@ -324,8 +325,12 @@ def test_no_memory(self): _testcapi.set_nomemory(0) l = [None] """) - _, _, err = assert_python_failure("-c", code) - self.assertIn("MemoryError", err.decode("utf-8")) + rc, _, _ = assert_python_failure("-c", code) + if support.MS_WINDOWS: + # STATUS_ACCESS_VIOLATION + self.assertNotEqual(rc, 0xC0000005) + else: + self.assertNotEqual(rc, -int(signal.SIGSEGV)) if __name__ == "__main__": unittest.main()