Redesigning the autopkgtest controller/workers CI system for Ubuntu and Debian

Andy Doan andy.doan at canonical.com
Thu Mar 13 23:31:18 UTC 2014


On 03/13/2014 12:52 PM, Martin Pitt wrote:
> Jean-Baptiste Lallement [2014-03-13 17:51 +0100]:
>>> > >This needs some refinement as we can have many runs with the same
>>> > >package version, and for failed runs we won't even have a package
>>> > >version. So perhaps
>>> > >
>>> > >  trusty/armhf/foopkg/<timestamp>/
>>> > >
>> >I need to think more about it but I can imagine situations where it
>> >might not be enough especially when several packages trigger a test
>> >for the same package.
> Yes, exactly. What'd we ideally need is some kind of atomic global
> counter in swift, or locking. Perhaps Andy or Evan have some idea
> about that how that's possible (I didn't find something like that).

I'm a little confused but the rabbit messages do include some attributes 
that might help with this:

<http://code.google.com/p/py-amqplib/source/browse/amqplib/client_0_8/basic_message.py#48>

would the timestamp + message_id help?




More information about the autopkgtest-devel mailing list