ForrestBot build for forrest-seed FAILED

2011-03-28 Thread Forrestbot
Automated build for forrest-seed FAILED
Log attached.

--
Forrestbot run ended at 28 March 09:07 AM
Using Forrest 0.10-dev
Forrestbot administrator: Forrest developers
--

 [echo] 
  ... Forrest render START 2011-03-28 09:04:07
  ... Rendering docs in 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed


check-java-version:
 [echo] This is apache-forrest-0.10-dev
 [echo] Using Java 1.6 from /usr/local/jdk1.6.0/jre
 [echo] Using Apache Ant version 1.7.1 compiled on September 26 2008 from 
/home/forrest/sources/forrest-trunk/tools/ant

init-props:
[mkdir] Created dir: 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp

echo-settings-condition:

echo-settings:

check-skin:

init-proxy:

fetch-skins-descriptors:

fetch-skin:

unpack-skins:

init-skins:

fetch-plugins-descriptors:
 [copy] Copying 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp
 [copy] Copying 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp
 [echo] Fetching plugins descriptor: 
http://forrest.apache.org/plugins/plugins.xml
  [get] Getting: http://forrest.apache.org/plugins/plugins.xml
  [get] To: 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/plugins-1.xml
  [get] local file date : Sun Jan 09 15:45:12 UTC 2011
  [get] Not modified - so not downloaded
 [echo] Fetching plugins descriptor: 
http://forrest.apache.org/plugins/whiteboard-plugins.xml
  [get] Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
  [get] To: 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/plugins-2.xml
  [get] local file date : Wed Mar 02 00:45:49 UTC 2011
  [get] Not modified - so not downloaded
 [echo] Plugin list loaded from 
http://forrest.apache.org/plugins/plugins.xml.
 [echo] Plugin list loaded from 
http://forrest.apache.org/plugins/whiteboard-plugins.xml.

init-plugins:
[mkdir] Created dir: 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/webapp/conf
 [copy] Copying 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp
 [copy] Copying 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp
 [copy] Copying 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp
 [copy] Copying 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp
 [copy] Copying 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp
 [echo] 
  --
  Installing plugin: org.apache.forrest.plugin.output.pdf
  --
   

check-plugin:
 [echo] org.apache.forrest.plugin.output.pdf is available in the build dir. 
Trying to update it...

init-props:

echo-settings-condition:

echo-settings:

init-proxy:

fetch-plugins-descriptors:

fetch-plugin:
 [echo] Trying to find the description of 
org.apache.forrest.plugin.output.pdf in the different descriptor files
 [echo] Using the descriptor file 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/plugins-1.xml...
 [xslt] Processing 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/plugins-1.xml 
to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/pluginlist2fetchbuild.xml
 [xslt] Loading stylesheet 
/home/forrest/sources/forrest-trunk/main/var/pluginlist2fetch.xsl

fetch-local-unversioned-plugin:

get-local:
 [echo] Trying to locally get org.apache.forrest.plugin.output.pdf
 [echo] Looking in local /home/forrest/sources/forrest-trunk/plugins
 [echo] Found !

init-build-compiler:

echo-init:

init:

compile:

jar:

local-deploy:
 [echo] Locally deploying org.apache.forrest.plugin.output.pdf

build:
 [echo] Plugin org.apache.forrest.plugin.output.pdf deployed ! Ready to 
configure

fetch-remote-unversioned-plugin-version-forrest:

fetch-remote-unversioned-plugin-unversion-forrest:

has-been-downloaded:

downloaded-message:

uptodate-message:

not-found-message:
 [echo] Fetch-plugin Ok, installing !

unpack-plugin:

install-plugin:

configure-plugin:

configure-output-plugin:
 [echo] Mounting output plugin: org.apache.forrest.plugin.output.pdf
 [xslt] Processing 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/output.xmap to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/output.xmap.new
 [xslt] Loading stylesheet 
/home/forrest/sources/forrest-trunk/main/var/pluginMountSnippet.xsl
 [move] Moving 1 file to 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp

configure-plugin-locationmap:
 [echo] Mounting plugin locationmap for org.apache.forrest.plugin.output.pdf
 [xslt] Processing 
/home/forrest/config/forrestbot-trunk/conf/work/forrest-seed/tmp/locationmap.xml
 to 

Re: Locationmap rewrite example, perhaps zone network glitch

2011-03-28 Thread Brian M Dube
On Fri, Mar 18, 2011 at 05:47:17PM +1100, David Crossley wrote:
 Brian M Dube wrote:
  David Crossley wrote:
   Forrestbot wrote:
[ snip ]
 [java] X [0] 
/home/forrest/config/forrestbot-trunk/sources/forrest-seed/src/documentation/content/xdocs/rewrite.index
  BROKEN: No pipeline matched request: 
/home/forrest/config/forrestbot-trunk/sources/forrest-seed/src/documentation/content/xdocs/rewrite.index
 [java] java.lang.NullPointerException
 [java] at 
org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:563)
[ snip ]
   
   I don't know what causes these occasional failures.
   Could it be a network glitch on the zone server.
   Can Forrest handle it better.
   Need to look into the Cocoon logfiles on our zone server.
  
  Need to look soon after the failure, or we temporarily suspend log
  pruning. I hadn't noticed how short-lived the logs are until I went to
  check on this and noticed the last failure is already pruned.
 
 I updated the f.a.o/zone.html doc to better explain the log files.
 Yes the Cocoon ones are of course re-generated on each hourly run.
 Perhaps we could add some post-processing to $CONFIG/run-forrestbot.sh
 to save the Cocoon logs if there is a non-successful build.

I see nothing revealing in the logs from the last failure.

I modified a local seed to try this link rewriting example with a name
that is known not to resolve to IP, and the failure mode is the same
as we are seeing with the zone. An occasional DNS issue?

Also, the NPE quoted above is resolved for me by adding one check for
null to the Cocoon source. Why it is null for our use case and not for
Cocoon's, I haven't investigated.

-Brian