mtest: Inline try_wait_one using asyncio.wait_for

[QuLogic]

Although the former accepts multiple awaitables, it is only ever called with a single one, so just use wait_for instead.

Additionally, the try_wait_one fails in Python 3.11, as Process.wait() returns a coroutine, and asyncio.wait only accepts tasks, so it errors out.

[codecov]

Codecov Report

Merging #10633 (fdeef46) into master (1e1dee7) will decrease coverage by 0.00%.
The diff coverage is 14.28%.

@@            Coverage Diff             @@
##           master   #10633      +/-   ##
==========================================
- Coverage   68.82%   68.82%   -0.01%     
==========================================
  Files         406      406              
  Lines       88062    88066       +4     
  Branches    19560    19566       +6     
==========================================
  Hits        60612    60612              
- Misses      22871    22875       +4     
  Partials     4579     4579              

Impacted Files	Coverage Δ
mesonbuild/mtest.py	77.11% <14.28%> (-0.11%)	⬇️
mtest.py	77.04% <0.00%> (-0.11%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1e1dee7...fdeef46. Read the comment docs.

[eli-schwartz]

@bonzini does this look right to you?

[bonzini]

Yes, it does.

[bonzini]

Additionally, the try_wait_one fails in Python 3.11, as Process.wait() returns a coroutine, and asyncio.wait only accepts tasks, so it errors out

@QuLogic is this a documented change? If not we should report a bug.

[QuLogic]

It was deprecated in 3.8, and scheduled for removal in 3.11: https://docs.python.org/3/library/asyncio-task.html#asyncio.wait

[bonzini]

Ah I interpreted that as "Process.wait() returns a coroutine in 3.11 instead of another kind of future", thanks.

[eli-schwartz]

Hmm, I tried to run the Meson testsuite with a warning filter that turns deprecations into errors, and I got a bunch of failures. But I never made it as far as this, I don't think. Instead, meson test seems to immediately error out with:

[0/1] Running all tests.
Traceback (most recent call last):
  File "/home/eschwartz/git/meson/mesonbuild/mesonmain.py", line 153, in run
    return options.run_func(options)
  File "/home/eschwartz/git/meson/mesonbuild/mtest.py", line 2049, in run
    return th.doit()
  File "/home/eschwartz/git/meson/mesonbuild/mtest.py", line 1726, in doit
    self.run_tests(runners)
  File "/home/eschwartz/git/meson/mesonbuild/mtest.py", line 1864, in run_tests
    loop = asyncio.get_event_loop()
DeprecationWarning: There is no current event loop

ERROR: Unhandled python exception

    This is a Meson bug and should be reported!