[Piuparts-devel] rescheduling broken

[Holger Levsen]

Hi,

On Dienstag, 2. April 2013, Andreas Beckmann wrote:
> > what does that mean exactly? 113 passed rescheduled and 31 failed?
> 
> echo "$SECTION: $RCOUNT/$ECOUNT/$UCOUNT"
> 
> 119 rescheduled, 31 expired, 0 obsolete
> 
> rescheduled = put hardlink into recycle/
> expire = delete from pass/fail because log is older than expire delay
> obsolete = delete from recycle/ because no matching log exists
> 
[...]
> 
> rescheduling does not delete any logs, nothing will be recycled as long
> as there is other work to be done. Logs are just *marked* for recycling
> (up to a certain limit of logs).
> 
> Expiration is the thing that might interfere with your expected behavior
> if the "backlog" is larger that what can be processed in between logs
> getting recyclied and expired.

thanks, also for putting this into the scrips / docs! Much appreciated.

I still have another rescheduling question but I'll leave this for when piatti 
is running the latest code again...


cheers,
	Holger


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20130413/43c1148c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20130413/43c1148c/attachment.pgp>