Hrmm, should I be concerned with the following output?

modificationcheck:
     [echo] Checking for modifications...
[CVSElement] Executing: cvs -d /usr/local/cvs -q log -N "-d>2002-03-02 04:24:55 GMT"
[CVSElement] [modificationset] Too much repository activity...sleeping for: 26254.802 seconds.

Here is the relevant part of my build.xml file:

    <target name="modificationcheck" depends="init" description="Check modifications since last build">
        <taskdef name="modificationset"
                 classname="net.sourceforge.cruisecontrol.ModificationSet">
            <classpath refid="classpath"/>
        </taskdef>
        <echo message="Checking for modifications..."/>
        <modificationset lastbuild="${lastBuildAttemptTime}"
                                 quietperiod="30"
                                 dateformat="yyyy-MMM-dd HH:mm:ss">
            <cvselement cvsroot="${cvs.repository}"/>
        </modificationset>
    </target>

Is my "continuous" build really going to be sleeping for 8 hours??

(I'm just trying to get the helloWorld example to work as a proof-of-concept.
A lot of modifications were necessary...the nested <classpath> element in
taskdef, for example.  I also had to change the build.dir, etc to prefix it
with "../" in order to get cvs to stop complaining about not being able to
do a "cvs log" in those directories...  Has anyone else attempted to get
the example working out of the box?  Am I doing something wrong?)

-Paul