Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #16278
| From | Timo Röhling <roehling@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python, linux.debian.bugs.dist |
| Subject | Re: Bug#1024971: pybuild: should fail when the result of running tests is "Ran 0 tests in 0.000s" |
| Date | 2024-09-13 11:00 +0200 |
| Message-ID | <JmajL-bWRW-5@gated-at.bofh.it> (permalink) |
| References | <FwzIZ-6MUo-9@gated-at.bofh.it> <JkqCl-aRPf-9@gated-at.bofh.it> |
| Organization | The Debian Project |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
Hi Stefano, * Stefano Rivera <stefanor@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. 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. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: Bug#1024971: pybuild: should fail when the result of running tests is "Ran 0 tests in 0.000s" Stefano Rivera <stefanor@debian.org> - 2024-09-08 16:00 +0200
Re: Bug#1024971: pybuild: should fail when the result of running tests is "Ran 0 tests in 0.000s" Scott Kitterman <debian@kitterman.com> - 2024-09-08 19:30 +0200
Re: Bug#1024971: pybuild: should fail when the result of running tests is "Ran 0 tests in 0.000s" Louis-Philippe Véronneau <pollo@debian.org> - 2024-09-12 17:40 +0200
Re: Bug#1024971: pybuild: should fail when the result of running tests is "Ran 0 tests in 0.000s" Julian Gilbey <julian@d-and-j.net> - 2024-09-08 23:40 +0200
Re: Bug#1024971: pybuild: should fail when the result of running tests is "Ran 0 tests in 0.000s" Stefano Rivera <stefanor@debian.org> - 2024-09-09 10:40 +0200
Re: Bug#1024971: pybuild: should fail when the result of running tests is "Ran 0 tests in 0.000s" Julian Gilbey <julian@d-and-j.net> - 2024-09-09 17:30 +0200
Re: Bug#1024971: pybuild: should fail when the result of running tests is "Ran 0 tests in 0.000s" Stefano Rivera <stefanor@debian.org> - 2024-09-10 17:10 +0200
Re: Bug#1024971: pybuild: should fail when the result of running tests is "Ran 0 tests in 0.000s" Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-09-12 16:30 +0200
Re: Bug#1024971: pybuild: should fail when the result of running tests is "Ran 0 tests in 0.000s" Stefano Rivera <stefanor@debian.org> - 2024-09-12 16:30 +0200
Re: Bug#1024971: pybuild: should fail when the result of running tests is "Ran 0 tests in 0.000s" Stefano Rivera <stefanor@debian.org> - 2024-09-09 10:40 +0200
Re: Bug#1024971: pybuild: should fail when the result of running tests is "Ran 0 tests in 0.000s" Timo Röhling <roehling@debian.org> - 2024-09-13 11:00 +0200
csiph-web