Hi Ian,
On 04-05-18 13:08, Ian Jackson wrote:
> Ian Jackson writes ("Re: Dealing with ci.d.n for package regressions"):
>> I hadn't realissed that _test_ dependencies would trigger retests, as
>> well as actual package dependencies.
>
> Having read Mattia
Hi Ian,
On 04-05-18 12:50, Ian Jackson wrote:
> Doing as you suggest for a real test feels wrong, since it involves
> denormalising (in the relational database sense) the dependency graph.
>
> But I guess I could introduce a test which does nothing, but which has
> as direct dependencies the indi
Hi Chris,
On 04-05-18 01:35, Chris Lamb wrote:
>>> ie. 75 out of "top" 100 packages according to popcon are missing
>>> autopkgtests.
>>
>> Yes, go provide patches to add them ;) But let's make them smart.
>
> Well, you're pushing at an open door with me with the "patches
> welcome" call to arms
Hi Ian,
Can we carry this discussion over to debian...@lists.debian.org (added
in CC now)?
On 04-05-18 15:24, Ian Jackson wrote:
> James Clarke writes ("Re: Dealing with ci.d.n for package regressions"):
>> On Fri, May 04, 2018 at 11:55:56AM +0100, Ian Jackson wrote:
>
Chris Lamb wrote:
> I can hack together quick things like:
I just noticed that UDD has lintian results, so you can just write
this as:
(Spoilers: I'm not a SQL programmer)
SELECT source, CASE (SELECT COUNT(*) FROM lintian
WHERE package = source AND package_type = 'source' AND
tag = 'te
Paul Gevers writes ("Dealing with ci.d.n for package regressions"):
> As I just announced on d-d-a¹, we have enabled autopkgtest usage for
> unstable-to-testing migration.
I observe that the tests done for this are done without building the
source, where this is a feature advertised by the test su
James Clarke writes ("Re: Dealing with ci.d.n for package regressions"):
> On Fri, May 04, 2018 at 11:55:56AM +0100, Ian Jackson wrote:
> > Is that documented somewhere ? I can't find it here
> > https://manpages.debian.org/stretch/dpkg-dev/dpk
On Fri, 2018-05-04 at 12:08:31 +0100, Ian Jackson wrote:
> Ian Jackson writes ("Re: Dealing with ci.d.n for package regressions"):
> > I hadn't realissed that _test_ dependencies would trigger retests, as
> > well as actual package dependencies.
>
> Having r
On Fri, May 04, 2018 at 11:55:56AM +0100, Ian Jackson wrote:
> Mattia Rizzolo writes ("Re: Dealing with ci.d.n for package regressions"):
> > On Thu, May 03, 2018 at 10:38:45PM +0200, Paul Gevers wrote:
> > > Just add it as a test dependency in one of your tests?
>
Ian Jackson writes ("Re: Dealing with ci.d.n for package regressions"):
> I hadn't realissed that _test_ dependencies would trigger retests, as
> well as actual package dependencies.
Having read Mattia's message, and looking at the Testsuite-Triggers
line which is autoge
Mattia Rizzolo writes ("Re: Dealing with ci.d.n for package regressions"):
> On Thu, May 03, 2018 at 10:38:45PM +0200, Paul Gevers wrote:
> > Just add it as a test dependency in one of your tests?
>
> Just to share a bit that doesn't seem to be of public know
Paul Gevers writes ("Re: Dealing with ci.d.n for package regressions"):
> On 03-05-18 14:12, Ian Jackson wrote:
> > 3. "Required age increased by 10 days because of autopkgtest"
> > seems to appear when either (i) when there are tests that should be
> >
Hi Paul,
> > ie. 75 out of "top" 100 packages according to popcon are missing
> > autopkgtests.
>
> Yes, go provide patches to add them ;) But let's make them smart.
Well, you're pushing at an open door with me with the "patches
welcome" call to arms :)
But is there not value to even the smalle
Hi Chris,
On 03-05-18 20:13, Chris Lamb wrote:
> Secondly, I was just wondering if you are collecting statistics
> over what percentage of packages have autopkgtests, or, perhaps
> more usefully which special/important packages have such tests?
https://ci.debian.net/status/ has a bit. Regarding i
On Thu, May 03, 2018 at 10:38:45PM +0200, Paul Gevers wrote:
> > 4. Can we have a way to trigger tests from updates of non-direct
> > rdepends ? At some point in the future maybe we will run tests of
> > whole batches of updates and then have some algorithm to chop out
> > what the failures are ca
Hi Ian,
On 03-05-18 14:12, Ian Jackson wrote:
>
Skipped two point that Niels already covered.
> 3. "Required age increased by 10 days because of autopkgtest"
> seems to appear when either (i) when there are tests that should be
> run but which haven't completed and (ii) when some tests newly fai
Hi Paul,
> And finally, thanks to all the people that helped and contributed to
> make this possible, 5 years after the initial announcement⁷.
First, thank you for pushing this!
Secondly, I was just wondering if you are collecting statistics
over what percentage of packages have autopkgtests, or
Ian Jackson:
> Paul Gevers writes ("Dealing with ci.d.n for package regressions"):
>> As I just announced on d-d-a¹, we have enabled autopkgtest usage for
>> unstable-to-testing migration.
>
> This is great.
>
> I have some suggestions/observations, looking particularly at
> https://release.deb
Paul Gevers writes ("Dealing with ci.d.n for package regressions"):
> As I just announced on d-d-a¹, we have enabled autopkgtest usage for
> unstable-to-testing migration.
This is great.
I have some suggestions/observations, looking particularly at
https://release.debian.org/britney/update_excu
19 matches
Mail list logo
