[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Trigger vs test log

Hi wferi,

[Changed the e-mail address to the CI list]

On 19-04-2019 07:58, wferi@niif.hu wrote:
> I'd like to better understand the output of this wonderful tool you
> provide.  I'm looking at the latest testing/amd64 log of pacemaker:
> https://ci.debian.net/data/packages/testing/amd64/p/pacemaker/2268682.log 
> The "Trigger" column says libqb/1.0.4-2, which makes perfect sense,
> because that's a freshly uploaded dependency, and the log indeed starts
> with --pin-packages=unstable=src:libqb, but then unexpectedly goes on to
> Get:2 http://deb.debian.org/debian unstable/main amd64 libqb0 amd64 1.0.4-1 [140 kB]
> which is the previous version.  Is this some synchronisation issue, or
> do I misunderstand to point of this test?

Yes, synchronization. The migration software already knows about the new
version and request test for it. The test is dispatched to one of the
ci.debian.net workers which just runs $(apt install) against
deb.debian.org. Sometimes we hit a mirror that is not as up-to-date as
we wish. I *may* try to check better in the future, but it needs a lot
of code to get this information at the proper place, so it's not high on
my list.


Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: