Bug#1024971: pybuild: should fail when the result of running tests is "Ran 0 tests in 0.000s"

[Timo Röhling]

Hi Stefano,

* Stefano Rivera <stefa...@debian.org> [2024-09-08 15:43]:

To fix these build failures, package maintainers would have these
options:

1. Get the build to run some unit tests (assuming they exist),
2. override_dh_auto_test with something noop,
3. export PYBUILD_DISABLE=test,
4. We could make this failure opt-in in dh-python. Maybe via an explicit
  --test-unittest option that selects the unittest runner. If you don't
  explicitly select this runner, you'd get an attempt to run tests by
  with unittest, and no failure if no tests are found.

Maybe we can start by making missing tests in autopkgtest fail? As you need to opt-in via "Testsuite: autopkgtest-pkg-pybuild", we can be quite certain that missing tests are not intentional.

Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling                                       │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀   ╰────────────────────────────────────────────────────╯

I think that would work very nicely together with option 4 for the build itself. You might even use the "Testsuite" setting as opt-in flag, but that is probably taking it too far.

signature.asc
Description: PGP signature