[Bug 2051977] [NEW] Unittest picking up no test is flagged as a failure with python 3.12

Launchpad Bug Tracker 2051977 at bugs.launchpad.net
Fri Feb 2 07:50:54 UTC 2024


You have been subscribed to a public bug by Pushkar Kulkarni (pushkarnk):

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

** Affects: factory-boy (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Unittest picking up no test is flagged as a failure with python 3.12
https://bugs.launchpad.net/bugs/2051977
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list