From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6135 invoked by alias); 11 Jun 2004 06:17:52 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 6115 invoked from network); 11 Jun 2004 06:17:49 -0000 Received: from unknown (HELO smtp811.mail.sc5.yahoo.com) (66.163.170.81) by sourceware.org with SMTP; 11 Jun 2004 06:17:49 -0000 Received: from unknown (HELO new-host.peterslan) (sampln@sbcglobal.net@67.121.190.239 with plain) by smtp811.mail.sc5.yahoo.com with SMTP; 11 Jun 2004 06:17:49 -0000 Subject: Bug in acp-independent action code From: Lincoln Peters To: Xconq list Content-Type: text/plain Message-Id: <1086934709.12177.4833.camel@odysseus> Mime-Version: 1.0 Date: Fri, 11 Jun 2004 06:17:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2004/txt/msg00522.txt.bz2 It would appear that, if an acp-independent unit executes a build task that depends on a certain material (as per unit-consumption-per-cp), and it runs out of the material before it can complete the build task, it will often abort the task and go into reserve, whereas it should go into reserve but keep the plan. It took me a while to pin this bug down, since an acp-independent unit with no task assigned automatically resumes building any incomplete units that occupy it. Consequently, it will build at least one unit despite the bug, and so it initially appeared to be a bug in the code that handles the number of units built as the result of a single build task (e.g. you tell it to build 99 knights and it only builds 1). --- Lincoln Peters Air is water with holes in it.