-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
Currently test runs are failing with Python 3.4 and coverage. The error message is at first nonsensical:
... [2021/06/26 01:01:09.453] gcc -pthread -shared -Wl,--enable-new-dtags,-rpath,/opt/python/3.4/lib build/temp.linux-x86_64-3.4/pymongo/_cmessagemodule.o build/temp.linux-x86_64-3.4/bson/buffer.o -L/opt/python/3.4/lib -lpython3.4m -o /data/mci/8522dad9ba0485694eebaebcf0b37dc5/src/pymongo/_cmessage.cpython-34m.so [2021/06/26 01:01:10.039] /opt/python/3.4/bin/python3: can't open file 'run': [Errno 2] No such file or directory
The problem is we're passing coverage arguments ("run --branch") straight to the python interpreter, rather than to the coverage binary. That happened in the following commit, which coincides with the beginning of the CI test failures:
I have no idea why this only breaks Python 3.4. All other versions run as expected.