$ make plague /usr/bin/plague-client build sylpheed sylpheed-2_0_0-1 devel Package sylpheed enqueued. $ plague-client list | grep syl $ $ plague-client list email bugs.michael | grep sylp $ $ plague-client list email bugs.michael 137: inkscape (inkscape-0_42-1_fc5) bugs.michael failed hammer3.fedora.redhat.com(x86_64): fd8220e02c46059b741652237ce8d70904b11da8 done/failed hammer2.fedora.redhat.com(i386): 820ffdd3b16c96572bc477511037074e46a87696 done/killed 226: glunarclock (glunarclock-0_32_4-1_fc4) bugs.michael failed Another try: $ make plague /usr/bin/plague-client build sylpheed sylpheed-2_0_0-1 devel Package sylpheed enqueued. $ plague-client list | grep syl $
I'm seeing the same problem right now with nco. I just ran: $ cd rpms/nco/FC-4 $ make plague /usr/bin/plague-client build nco nco-3_0_1-4_fc4 fc4 Package nco enqueued. but the build doesn't start. And waiting a half-hour and re-trying doesn't help. The odd thing is that it worked just fine for me yesterday.
This is the failure case when the server gets wedged. Probably one sane thing to do here is to have the client not get back a success from the server until after the job is successfully committed to the jobdb. That at least gets rid of silent failures. The second thing is fixing things so we don't end up in this state. Adding dcbw to the cc list since he's spearheading most of the actual writing of code.
Fixed in CVS.