| 2024-02-01 18:55:56 |
Pushkar Kulkarni |
bug |
|
|
added bug |
| 2024-02-01 18:57:32 |
Pushkar Kulkarni |
description |
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 |
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 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 |
|
| 2024-02-01 19:00:59 |
Pushkar Kulkarni |
description |
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 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 |
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 |
|
| 2024-02-01 19:13:03 |
Pushkar Kulkarni |
merge proposal linked |
|
https://code.launchpad.net/~pushkarnk/ubuntu/+source/factory-boy/+git/factory-boy/+merge/459838 |
|
| 2024-02-02 07:50:54 |
Pushkar Kulkarni |
bug |
|
|
added subscriber Ubuntu Sponsors |
| 2024-02-07 13:54:02 |
Graham Inggs |
factory-boy (Ubuntu): assignee |
|
Graham Inggs (ginggs) |
|
| 2024-02-07 13:54:05 |
Graham Inggs |
factory-boy (Ubuntu): status |
New |
In Progress |
|
| 2024-02-07 13:54:07 |
Graham Inggs |
removed subscriber Ubuntu Sponsors |
|
|
|
| 2024-02-07 14:02:25 |
Graham Inggs |
factory-boy (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2024-02-08 01:34:37 |
Launchpad Janitor |
factory-boy (Ubuntu): status |
Fix Committed |
Fix Released |
|
