From a69107b33587b0fb262063971d7a0794cee613d4 Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Sat, 8 Mar 2025 19:21:46 +0100 Subject: [PATCH] [3.12] gh-130917: update timer and workload in test_signal (GH-130918) (#130968) The workload to advance the virtual timeout is too lightweight for some platforms. As result the test goes in timeout as it never reaches the end of the timer. By having a heavier workload, the virtual timer advances rapidly and the SIGVTALRM is sent before the timeout. (cherry picked from commit 78790811989ab47319e2ee725e0c435b3cdd21ab) Co-authored-by: Diego Russo --- Lib/test/test_signal.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Lib/test/test_signal.py b/Lib/test/test_signal.py index a45527d7315d..9a01ad0dd5ce 100644 --- a/Lib/test/test_signal.py +++ b/Lib/test/test_signal.py @@ -839,11 +839,11 @@ class ItimerTest(unittest.TestCase): def test_itimer_virtual(self): self.itimer = signal.ITIMER_VIRTUAL signal.signal(signal.SIGVTALRM, self.sig_vtalrm) - signal.setitimer(self.itimer, 0.3, 0.2) + signal.setitimer(self.itimer, 0.001, 0.001) for _ in support.busy_retry(support.LONG_TIMEOUT): # use up some virtual time by doing real work - _ = pow(12345, 67890, 10000019) + _ = sum(i * i for i in range(10**5)) if signal.getitimer(self.itimer) == (0.0, 0.0): # sig_vtalrm handler stopped this itimer break @@ -860,7 +860,7 @@ class ItimerTest(unittest.TestCase): for _ in support.busy_retry(support.LONG_TIMEOUT): # do some work - _ = pow(12345, 67890, 10000019) + _ = sum(i * i for i in range(10**5)) if signal.getitimer(self.itimer) == (0.0, 0.0): # sig_prof handler stopped this itimer break -- 2.47.3