[Piuparts-devel] protocol changes for idle and arch

Dave Steele dsteele at gmail.com
Mon Jun 4 20:21:10 UTC 2012

On Mon, Jun 4, 2012 at 1:46 PM, Dave Steele <dsteele at gmail.com> wrote:
> But, as you point out elsewhere, this blocks the slave from uploading
> its results.

Scratch that. find_packages_ready_for_testing() includes reserved
packages, so master won't go idle until the reserve list is cleared.

So, the 'idle' response gives a simple, clean way for the master to
quickly report the idle state to the slave. The most obvious
alternatives would be more messy (work with/around a PackageDB object
that has not been populated) or inefficient (always load Packages.gz).

That also means that the only things that invalidate the idle state
are an update to the repository, or non-slave intervention in the
master section directory tree. A 'retest' utility could address the
second case. Is there any thought of working with the mirror push
protocol to speed up the first?

More information about the Piuparts-devel mailing list