Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #15134
| From | Andrey Rakhmatullin <wrar@wrar.name> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Package testing with Salsa CI for new packages |
| Date | 2023-08-18 18:30 +0200 |
| Message-ID | <H4awh-2L8W-5@gated-at.bofh.it> (permalink) |
| References | <H3MWZ-2whZ-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Aug 17, 2023 at 05:10:08PM +0200, Paul Boddie wrote: > Here, it would seem that the most prudent approach is to use the Salsa CI > service instead of trying to get the test suite to run during the package > build process. You should do both if possible, assuming that by "Salsa CI service" you mean autopkgtests which you can, and IMO should, also run locally. > One motivation for doing so involves not having to specify > build dependencies for packages only needed for test suite execution, which > itself requires the invocation of gbp buildpackage with --extra-package > arguments since some packages are completely new to Debian. This is fine. Not to mention that the same problem exists for autopkgtests, as you say below. > I have also found it difficult to persuade the tests to run successfully > during the build process. A few of these attempt to invoke the moin program, > but this cannot be located since it is not installed in the build environment. This should also be fine, unless it's completely impossible to run it without installing into /. > However, one conclusion is that testing a system, as some of the > test cases appear to do, and as opposed to testing library functionality, is > not necessarily appropriate when directed by something like dh_auto_test. If there are tests that can't be run at build time you can skip those. You can even ask the upstream to provide tool arguments to simplify that.
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Package testing with Salsa CI for new packages Paul Boddie <paul@boddie.org.uk> - 2023-08-17 17:20 +0200
Re: Package testing with Salsa CI for new packages Carles Pina i Estany <carles@pina.cat> - 2023-08-18 10:00 +0200
Re: Package testing with Salsa CI for new packages Paul Boddie <paul@boddie.org.uk> - 2023-08-18 13:20 +0200
Re: Package testing with Salsa CI for new packages Carles Pina i Estany <carles@pina.cat> - 2023-08-18 16:20 +0200
Re: Package testing with Salsa CI for new packages Paul Boddie <paul@boddie.org.uk> - 2023-08-18 19:10 +0200
Re: Package testing with Salsa CI for new packages Carles Pina i Estany <carles@pina.cat> - 2023-08-18 20:00 +0200
Re: Package testing with Salsa CI for new packages Paul Boddie <paul@boddie.org.uk> - 2023-08-19 19:10 +0200
Re: Package testing with Salsa CI for new packages Carles Pina i Estany <carles@pina.cat> - 2023-08-19 20:40 +0200
Re: Package testing with Salsa CI for new packages Paul Boddie <paul@boddie.org.uk> - 2023-08-20 00:50 +0200
Re: Package testing with Salsa CI for new packages Carles Pina i Estany <carles@pina.cat> - 2023-08-20 14:10 +0200
Re: Package testing with Salsa CI for new packages Paul Boddie <paul@boddie.org.uk> - 2023-08-20 23:20 +0200
Re: Package testing with Salsa CI for new packages Carles Pina i Estany <carles@pina.cat> - 2023-08-21 15:10 +0200
Re: Package testing with Salsa CI for new packages Paul Boddie <paul@boddie.org.uk> - 2023-08-21 19:20 +0200
Re: Package testing with Salsa CI for new packages Andrey Rakhmatullin <wrar@wrar.name> - 2023-08-18 18:30 +0200
Re: Package testing with Salsa CI for new packages Paul Boddie <paul@boddie.org.uk> - 2023-08-18 19:20 +0200
Re: Package testing with Salsa CI for new packages Andrey Rakhmatullin <wrar@wrar.name> - 2023-08-18 19:50 +0200
csiph-web