Unittest picking up no test is flagged as a failure with python 3.12

[Pushkar Kulkarni]

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 [2] to deem it as a failure [3].

I am not sure if we should investigate why no tests were ever (there's evidence for the last three releases) 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

[3] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/amd64/f/factory-boy/20240126_135906_d8a63@/log.gz

[Launchpad Janitor (janitor)]

This bug was fixed in the package factory-boy - 2.11.1-7ubuntu1

---------------
factory-boy (2.11.1-7ubuntu1) noble; urgency=medium

  * d/control/test: Comment out unit-test-p3 which runs no tests (LP: #2051977)

 -- Pushkar Kulkarni <email address hidden> Fri, 02 Feb 2024 00:32:02 +0530