Re: SRCPV / prserv problem

[Martin Jansa <martin.jansa@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]

On Wed, Aug 08, 2018 at 05:34:51PM +0200, Eric BENARD wrote:
> Hi,
> 
> I have a strange issue with a recipe fetching from git for which I fix the
> HASH in a conf file :
> I'm using PRSERV_HOST = "localhost:0"
> The recipe has PV = "gitr${SRCPV}" so I expect the package numbering to be
> handled by the prserv.
> 
> If I add a SRCREV_pn-mysw = "1ad58b2488ce91ce4d0c4aae4189108b0281aae6", I
> see in buildhistory :
> PV = gitrAUTOINC+1ad58b2488
> PKGV = gitr0+1ad58b2488
> 
> If I then fix the hash to 6bd8208a0754a23b5437cb34a361fc22d7dc0c3b, I see
> in buildhistory :
> -PKGV = gitr0+1ad58b2488
> +PKGV = gitr0+6bd8208a07
> +PKGR = r0.0
> which is expected

Is this really expected? It should get gitr1 here.

> But then if I come back to the hash
> 1ad58b2488ce91ce4d0c4aae4189108b0281aae6, I see :
> -PKGV = gitr2+6bd8208a07
> -PKGR = r0.1
> +PKGV = gitr0+1ad58b2488
> and thus I have the package numbering going backward with a QA error.

This is expected, when it gets 1ad58b2488 which is already recorded in
the database it will return the old number.

That's for multiple builders using different SRCREV and the same PRSERV,
they should get stable AUTOINC numbers, not incrementing both of these
every time they ask PRSERV.

> Do you have any idea on what is causing this behavior and where to dig to
> fix this ?

Checking the sqlite database for recorded AUTOINC numbers and hashes is
usually useful starting point.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]