Define test_search_anchor_at_beginning as CPU-heavy tests.

[corona10]

Currently test_search_anchor_at_beginning requires to be completed in an absolute time.
This can be flaky at low CPU environment or slow alternative implementation like RustPython.

I would like to suggest adding @support.requires_resource('cpu') to the test.

cpython/Lib/test/test_re.py

Lines 2285 to 2296 in 62aeb0e

	def test_search_anchor_at_beginning(self):
	s = 'x'*10**7
	with CPUStopwatch() as stopwatch:
	for p in r'\Ay', r'^y':
	self.assertIsNone(re.search(p, s))
	self.assertEqual(re.split(p, s), [s])
	self.assertEqual(re.findall(p, s), [])
	self.assertEqual(list(re.finditer(p, s)), [])
	self.assertEqual(re.sub(p, '', s), s)
	# Without optimization it takes 1 second on my computer.
	# With optimization -- 0.0003 seconds.
	self.assertLess(stopwatch.seconds, 0.1)

Linked PRs

• gh-117594: Require cpu resource to test_search_anchor_at_beginning #117595
• [3.12] gh-117594: Require cpu resource to test_search_anchor_at_beginning (g… #117616

[youknowone]

Thank you! Related RustPython CI failure is: https://github.com/RustPython/RustPython/actions/runs/8580508887/job/23516638468

[serhiy-storchaka]

Oh, I expected that there is no computer able to run modern Python and 300 times slower than my notebook.