From: Lincoln Peters <sampln@sbcglobal.net>
To: Xconq list <xconq7@sources.redhat.com>
Subject: Bug in acp-independent action code
Date: Fri, 11 Jun 2004 06:17:00 -0000 [thread overview]
Message-ID: <1086934709.12177.4833.camel@odysseus> (raw)
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
<sampln@sbcglobal.net>
Air is water with holes in it.
next reply other threads:[~2004-06-11 6:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 6:17 Lincoln Peters [this message]
2004-06-11 6:40 ` Hans Ronne
2004-06-12 6:45 ` Lincoln Peters
2004-06-12 9:01 ` Hans Ronne
2004-06-13 21:45 ` Hans Ronne
2004-06-14 23:34 ` Hans Ronne
2004-06-15 4:55 ` Lincoln Peters
2004-06-15 7:18 ` Hans Ronne
2004-06-15 20:51 ` Lincoln Peters
2004-06-16 4:08 ` New Wreck-Type Options Elijah Meeks
2004-06-16 13:49 ` Eric McDonald
2004-06-16 21:00 ` Bug in acp-independent action code Hans Ronne
2004-06-15 5:19 ` Eric McDonald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1086934709.12177.4833.camel@odysseus \
--to=sampln@sbcglobal.net \
--cc=xconq7@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).