Felix asked me to report the performance data for the lintian testsuite
I'm getting on my new desktop computer.
Let me first say I'm a very casual contributor to Lintian and I'm
certainly not in a position to judge if the testsuite takes too much
time to run or is too extensive by default. Take th
Felix Lechner wrote:
> > We do similar in some pkg-gnome packages, for example glib2.0 ships a
> > -tests package that contains "installed tests" which are compiled as
> > part of the package build and then executed during the autopkgtests.
>
> Should we ship all built test packages as part of our
On Wed, Jun 03, 2020 at 02:50:04AM +0200, Mattia Rizzolo wrote:
> On Wed, 3 Jun 2020, 1:09 am Felix Lechner,
> ...
> > On Fri, Apr 5, 2019 at 4:33 AM Iain Lane wrote:
> > >
> > > We do similar in some pkg-gnome packages, for example glib2.0 ships a
> > > -tests package that contains "installed te
On Wed, 3 Jun 2020, 1:09 am Felix Lechner,
wrote:
> Hi Chris,
>
> On Fri, Apr 5, 2019 at 4:33 AM Iain Lane wrote:
> >
> > We do similar in some pkg-gnome packages, for example glib2.0 ships a
> > -tests package that contains "installed tests" which are compiled as
> > part of the package build a
Hi Chris,
On Fri, Apr 5, 2019 at 4:33 AM Iain Lane wrote:
>
> We do similar in some pkg-gnome packages, for example glib2.0 ships a
> -tests package that contains "installed tests" which are compiled as
> part of the package build and then executed during the autopkgtests.
Should we ship all bui
On Thu, Apr 04, 2019 at 12:10:31PM -0700, Felix Lechner wrote:
> On Thu, Apr 4, 2019 at 10:42 AM Chris Lamb wrote:
> >
> > * I'm not sure *how* we can speed up the tests. I mean, they all
> >essentially involve building Debian packages with all the usual
> >debhelper calls, etc. Speeding
On Thu, Apr 4, 2019 at 12:19 PM Chris Lamb wrote:
>
> Felix Lechner wrote:
>
> > About 95% of the time is spent building packages, even though they
> > almost never change. The tests would run much faster if we shipped
> > pre-built packages.
>
> Another way to accomplish this could be that we co
On Thu, Apr 4, 2019 at 11:24 AM Balint Reczey
wrote:
>
> One criterion that came to my mind is filtering by severity, including
> errors for sure, but not pedantic ones.
The pedantic setting may become the default for tests, but very little
time is spent running Lintian.
Things may speed up a li
Balint Reczey wrote:
> One criterion that came to my mind is filtering by severity, including
> errors for sure, but not pedantic ones.
Mmm, unfortunately I think we would still want to know if, for
example, the runtime toolchain changes such that a pedantic tag
changes behaviour. :(
Felix Lechn
On Thu, Apr 4, 2019 at 10:42 AM Chris Lamb wrote:
>
> * I'm not sure *how* we can speed up the tests. I mean, they all
>essentially involve building Debian packages with all the usual
>debhelper calls, etc. Speeding *this* up is somewhat out-of-scope
>of this Lintian wishlist issue, a
Hi Chris,
On Thu, Apr 4, 2019 at 7:30 PM Chris Lamb wrote:
>
> tags 926409 + moreinfo
> thanks
>
> Hi Balint,
>
> > Lintian has a lot of tests which is great for coverage, but maybe some
> > of them could be skipped in autopkgtest runs.
>
> Interesting. I guess I would have three follow-up questi
tags 926409 + moreinfo
thanks
Hi Balint,
> Lintian has a lot of tests which is great for coverage, but maybe some
> of them could be skipped in autopkgtest runs.
Interesting. I guess I would have three follow-up questions here:
* On what criterion or criteria could we include or exclude tests
Package: lintian
Version: 2.11.0
Severity: wishlist
Hi,
Lintian has a lot of tests which is great for coverage, but maybe some
of them could be skipped in autopkgtest runs.
Currently autopkgtest takes ~1 wall clock hours on Debian's amd64 CI
[1], but Ubuntu runs autopkgtest on all architectures a
13 matches
Mail list logo
