The test unit-tests-p3 has been running 0 tests for a long time (perhaps since its addition in 2.11.1-2) but surely since 2.11.1-5 [1]. This was deemed as success until Python 3.12 decided to deem it as a failure [2].
I am not sure if we should investigate why no tests were picked up by `unit-test-p3`, in the short term (I tried running the unittests and a lot of them seem to fail). Perhaps, in the shorter term, we need to work around the new unittest behavior of 3.12.
The test unit-tests-p3 has been running 0 tests for a long time (perhaps since its addition in 2.11.1-2) but surely since 2.11.1-5 [1]. This was deemed as success until Python 3.12 decided to deem it as a failure [2].
I am not sure if we should investigate why no tests were picked up by `unit-test-p3`, in the short term (I tried running the unittests and a lot of them seem to fail). Perhaps, in the shorter term, we need to work around the new unittest behavior of 3.12.
[1] https:/ /autopkgtest. ubuntu. com/results/ autopkgtest- noble/noble/ amd64/f/ factory- boy/20220621_ 134009_ ccbc7@/ log.gz
[2] https:/ /github. com/python/ cpython/ pull/102051