test_overrunning_test_times_out is flaky

[altendky]

FAILED C:\hostedtoolcache\windows\Python\3.6.8\x86\lib\site-packages\qtrio_tests\test_pytest.py::test_overrunning_test_times_out

https://github.com/altendky/qtrio/pull/50/checks?check_run_id=828834279

2020-07-02T01:11:11.5061202Z E               subprocess.TimeoutExpired: Command '('c:\\hostedtoolcache\\windows\\python\\3.6.8\\x86\\python.exe', '-mpytest', '--basetemp=C:\\Users\\runneradmin\\AppData\\Local\\Temp\\pytest-of-runneradmin\\pytest-0\\test_overrunning_test_times_out0\\runpytest-0')' timed out after 6 seconds

At first glance it looks like @qtrio.host isn't timing out properly thus resulting in a subprocess timeout instead. It doesn't seem like the subprocess launch time should be sufficient to cause this but... usually it doesn't. So, maybe that's it and the subprocess timeout just (appropriately) needs a significant bump to reduce flakiness. Unless maybe we can come up with a better way.

qtrio/qtrio/_tests/test_pytest.py

Lines 4 to 23 in f81faa8

	def test_overrunning_test_times_out(testdir):
	"""The overrunning test is timed out."""
	test_file = rf"""
	import qtrio
	import trio
	@qtrio.host
	async def test(request):
	await trio.sleep({2 * qtrio._pytest.timeout})
	"""
	testdir.makepyfile(test_file)
	timeout = qtrio._pytest.timeout
	result = testdir.runpytest_subprocess(timeout=2 * qtrio._pytest.timeout)
	result.assert_outcomes(failed=1)
	result.stdout.re_match_lines(
	lines2=[f"E AssertionError: test not finished within {timeout} seconds"],
	)

[altendky]

Apparently that didn't fix it. All through poking at the macOS issues today Windows didn't fail once. Ugh.

https://github.com/altendky/qtrio/pull/58/checks?check_run_id=832969315

[altendky]

Been ok for awhile now... :|

[altendky]

*sigh*

https://github.com/altendky/qtrio/pull/90/checks?check_run_id=862991263