multiprocessing.Process.is_alive() incorrect if waitpid() was executed concurrently to it

Bug report
As per title. In my case I triggered the os.waitpid() using psutil library, but easily reproducible using os.waitpid, too.

Reproduction:

Python 3.9.5 (default, Nov 18 2021, 16:00:48) 
[GCC 10.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from multiprocessing import Process
>>> import os
>>> import time
>>> p = Process(target=time.sleep, args=(10,))
>>> p.start(); os.waitpid(p.pid, 0)
(17587, 0)
>>> p.is_alive()
True
>>> p.join() # Returns immediately
>>> 

I understand it's something of a corner case; however, join() behaves correctly here, so we definitely have enough info about whether the process is alive.

By the looks of it, if the process has been already waited on, poll() Popen method in multiprocessing returns None, which is interpreted as the process being still alive.

Your environment

• CPython versions tested on: 3.9.5, but main version seems affected
• Operating system and architecture: x64 Ubuntu Linux

先追蹤 multiprocessing.Process.is_alive()、Popen.poll() 路徑和 Process.join()，同時在 Linux 上重現並行 os.waitpid() 範例。比較每條路徑如何判定子行程已結束，然後加入回歸測試涵蓋範圍，顯示在子行程已經被等待之後，is_alive() 會回報 false，且 join() 仍會立即返回。