gump failures, please help
ok. after weeks of wrestling with gump to find out what the failures
are about, this last build gave some decent info.
See:
http://vmgump.apache.org/gump/public/velocity-engine/velocity-engine-test/gump_work/build_velocity-engine_velocity-engine-test.html
I think this section shows the main problem:
[junit] log: [debug] Velocity was not initialized! Calling init()...
[junit] [debug] Starting Apache Velocity v03092008 (compiled:
2008-09-03 18:37:33)
[junit] [debug] Default Properties File:
org/apache/velocity/runtime/defaults/velocity.properties
[junit] [debug] ResourceManager : No configuration information
for resource loader named 'string'. Skipping.
[junit] [debug] ResourceLoader instantiated:
org.apache.velocity.runtime.resource.loader.FileResourceLoader
[junit] [debug] Do unicode file recognition: false
[junit] [debug] FileResourceLoader : adding path
'/srv/gump/public/workspace/velocity-engine/test/resourceexists'
[junit] [debug] ResourceCache: initialized (class
org.apache.velocity.runtime.resource.ResourceCacheImpl) with class
java.util.Collections$SynchronizedMap cache map.
As you can see, the engine knows there are two resource loaders 'file'
and 'string'. It has path info for the 'file' resource loader, but it
has *no* info on the 'string' resource loader. But if you look at the
test case, it clearly adds info for both loaders:
velocity = new VelocityEngine();
velocity.setProperty(resource.loader, file,string);
velocity.setProperty(file.resource.loader.path, path);
velocity.setProperty(string.resource.loader.class,
StringResourceLoader.class.getName());
This code runs perfectly on my machine and probably on yours too. So,
what the hell? If you further peruse the output from the last gump
build (link above), you will see that the ResourceInstanceTestCase has
the same problem (no info for the 'testrl' resource loader).
The ResourceManager code producing that 'no config info' log message is:
String loaderName = (String) it.next();
StringBuffer loaderID = new StringBuffer(loaderName);
loaderID.append(.).append(RuntimeConstants.RESOURCE_LOADER);
ExtendedProperties loaderConfiguration =
rsvc.getConfiguration().subset(loaderID.toString());
if (loaderConfiguration == null)
{
log.debug(ResourceManager : No configuration
information for resource loader named ' +
loaderName + '. Skipping.);
continue;
}
Why this would work for 'file' and not for 'string' or 'testrl' is
currently a baffling mystery to me. My best guess at this point is
that it is due to some underlying change in Commons-Collections'
ExtendedProperties class. But that seems kind of unlikely. Any
insights? I'm about ready to give up and just find a workaround that
makes gump happy, but if there is a bug coming down the line, that
would not be helpful...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[GUMP@vmgump]: Project velocity-engine-test (in module velocity-engine) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project velocity-engine-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 20 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - velocity-engine-test : Velocity Templating engine Full details are available at: http://vmgump.apache.org/gump/public/velocity-engine/velocity-engine-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/velocity-engine/velocity-engine-test/gump_work/build_velocity-engine_velocity-engine-test.html Work Name: build_velocity-engine_velocity-engine-test (Type: Build) Work ended in a state of : Failed Elapsed: 53 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Djar.oro.dir=/srv/gump/public/workspace/jakarta-oro -Ddeprecation=false -Djar.commons-collections.version=04092008 -Dskip.jar.loading=true -Djar.commons-lang.dir=/srv/gump/public/workspace/apache-commons/lang/dist -Dversion=04092008 -Djar.commons-collections.dir=/srv/gump/public/workspace/apache-commons/collections/build -Djar.commons-lang.version=04092008 -Djar.oro.name=jakarta-oro -Djar.oro.version=04092008 test [Working Directory: /srv/gump/public/workspace/velocity-engine/build] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/velocity-engine/test:/srv/gump/public/workspace/velocity-engine/bin/test-classes:/srv/gump/public/workspace/velocity-engine/test/cpload/test1.jar:/srv/gump/public/workspace/velocity-engine/test/texen-classpath/test.jar:/srv/gump/public/workspace/velocity-engine/test/multiloader/test1.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-04092008.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-dep-04092008.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/packages/junit3.8.1/junit.jar:/s rv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/packages/avalon-logkit/avalon-logkit-2.1.jar:/srv/gump/public/workspace/apache-commons/collections/build/commons-collections-04092008.jar:/srv/gump/public/workspace/apache-commons/lang/commons-lang-04092008.jar:/srv/gump/public/workspace/logging-log4j-12/dist/lib/log4j-04092008.jar:/srv/gump/public/workspace/jdom/build/jdom.jar:/srv/gump/public/workspace/jakarta-servletapi-4/lib/servlet.jar:/srv/gump/public/workspace/jakarta-oro/jakarta-oro-04092008.jar:/srv/gump/packages/werken-xpath/werken-xpath-0.9.4.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-04092008.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-04092008.jar:/srv/gump/packages/antlr-2.7.6/antlr.jar:/srv/gump/public/workspace/hsqldb/lib/hsqldb.jar - [junit] [debug] ResourceManager : No configuration information found for resource loader named 'testrl' (id is testrl.resource.loader). Skipping it... [junit] [debug] ResourceCache: initialized (class org.apache.velocity.runtime.resource.ResourceCacheImpl) with class java.util.Collections$SynchronizedMap cache map. [junit] [debug] Loaded System Directive: org.apache.velocity.runtime.directive.Define [junit] [debug] Loaded System Directive: org.apache.velocity.runtime.directive.Break [junit] [debug] Loaded System Directive: org.apache.velocity.runtime.directive.Evaluate [junit] [debug] Loaded System Directive: org.apache.velocity.runtime.directive.Literal [junit] [debug] Loaded System Directive: org.apache.velocity.runtime.directive.Macro [junit] [debug] Loaded System Directive: org.apache.velocity.runtime.directive.Parse [junit] [debug] Loaded System Directive: org.apache.velocity.runtime.directive.Include [junit] [debug] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach [junit] [debug] Created '20' parsers. [junit] [debug] Velocimacro : velocimacro.library is not set. Trying default library: VM_global_library.vm [junit] [debug] Velocimacro : Default library not
[GUMP@vmgump]: Project velocity-texen-test (in module velocity-texen) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project velocity-texen-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 20 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - velocity-texen-test : Texen is a general purpose text generating utility based on ... Full details are available at: http://vmgump.apache.org/gump/public/velocity-texen/velocity-texen-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/velocity-texen/velocity-texen-test/gump_work/build_velocity-texen_velocity-texen-test.html Work Name: build_velocity-texen_velocity-texen-test (Type: Build) Work ended in a state of : Failed Elapsed: 5 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Ddeprecation=false -Dversion=04092008 -Dskip.jar.loading=true test [Working Directory: /srv/gump/public/workspace/velocity-texen/build] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/velocity-texen/bin/test-classes:/srv/gump/public/workspace/velocity-texen/bin/test:/srv/gump/public/workspace/velocity-texen/bin/test/texen-classpath.jar:/srv/gump/public/workspace/velocity-texen/bin/texen-04092008.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/packages/junit3.8.1/junit.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/apache-commons/collections/build/commons-collections-04092008.jar:/srv/gump/public/workspace/apache-commons/lang/commons-lan g-04092008.jar:/srv/gump/public/workspace/logging-log4j-12/dist/lib/log4j-04092008.jar:/srv/gump/public/workspace/jdom/build/jdom.jar:/srv/gump/packages/werken-xpath/werken-xpath-0.9.4.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-04092008.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-dep-04092008.jar:/srv/gump/public/workspace/velocity-anakia/bin/anakia-04092008.jar:/srv/gump/packages/antlr-2.7.6/antlr.jar - test-jar: [mkdir] Created dir: /srv/gump/public/workspace/velocity-texen/bin/test [jar] Building jar: /srv/gump/public/workspace/velocity-texen/bin/test/texen-classpath.jar test: [mkdir] Created dir: /srv/gump/public/workspace/velocity-texen/bin/test-reports [junit] Running org.apache.texen.ExtendedTexenTestCase [junit] Template results directory does not exist [junit] Created template results directory [junit] Generating to file bin/test/texen-generator/report [junit] Comparing result file 'bin/test/texen-generator/TurbineWeather.java' with compare file 'test/texen/compare/TurbineWeather.java' [junit] Comparing result file 'bin/test/texen-generator/TurbineWeatherService.java' with compare file 'test/texen/compare/TurbineWeatherService.java' [junit] Comparing result file 'bin/test/texen-generator/WeatherService.java' with compare file 'test/texen/compare/WeatherService.java' [junit] Comparing result file 'bin/test/texen-generator/book.txt' with compare file 'test/texen/compare/book.txt' [junit] Comparing result file 'bin/test/texen-generator/Text.txt' with compare file 'test/texen/compare/Text.txt' [junit] Template results directory does not exist [junit] Created template results directory [junit] Using classpath [junit] Generating to file bin/test/texen-generator-classpath/report [junit] org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource 'Control.vm' [junit] at org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(ResourceManagerImpl.java:483) [junit] at org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:354) [junit] at org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:1388) [junit] at org.apache.velocity.app.VelocityEngine.getTemplate(VelocityEngine.java:422) [junit] at org.apache.texen.Generator.getTemplate(Generator.java:321) [junit] at
Re: gump failures, please help
My suspicion has fallen on the fix done for this:
https://issues.apache.org/jira/browse/COLLECTIONS-271
which we also heard about here (for reference)
https://issues.apache.org/jira/browse/VELOCITY-567
because anything added through our setProperty method goes into an
ExtendedProperties whose values are passed into the final
ExtendedProperties via the combine() method. By circumventing the
ExtendedProperties.setProperty method in the patch for
COLLECTIONS-271, i'm thinking that the new props don't end up in
ExtendedProperties' keysAsListed array, which it uses for getKeys()
which the subset() method (and therefore, us) is entirely reliant
upon.
i'll ping the commons list
On Fri, Sep 5, 2008 at 11:13 AM, Nathan Bubna [EMAIL PROTECTED] wrote:
ok. after weeks of wrestling with gump to find out what the failures
are about, this last build gave some decent info.
See:
http://vmgump.apache.org/gump/public/velocity-engine/velocity-engine-test/gump_work/build_velocity-engine_velocity-engine-test.html
I think this section shows the main problem:
[junit] log: [debug] Velocity was not initialized! Calling init()...
[junit] [debug] Starting Apache Velocity v03092008 (compiled:
2008-09-03 18:37:33)
[junit] [debug] Default Properties File:
org/apache/velocity/runtime/defaults/velocity.properties
[junit] [debug] ResourceManager : No configuration information
for resource loader named 'string'. Skipping.
[junit] [debug] ResourceLoader instantiated:
org.apache.velocity.runtime.resource.loader.FileResourceLoader
[junit] [debug] Do unicode file recognition: false
[junit] [debug] FileResourceLoader : adding path
'/srv/gump/public/workspace/velocity-engine/test/resourceexists'
[junit] [debug] ResourceCache: initialized (class
org.apache.velocity.runtime.resource.ResourceCacheImpl) with class
java.util.Collections$SynchronizedMap cache map.
As you can see, the engine knows there are two resource loaders 'file'
and 'string'. It has path info for the 'file' resource loader, but it
has *no* info on the 'string' resource loader. But if you look at the
test case, it clearly adds info for both loaders:
velocity = new VelocityEngine();
velocity.setProperty(resource.loader, file,string);
velocity.setProperty(file.resource.loader.path, path);
velocity.setProperty(string.resource.loader.class,
StringResourceLoader.class.getName());
This code runs perfectly on my machine and probably on yours too. So,
what the hell? If you further peruse the output from the last gump
build (link above), you will see that the ResourceInstanceTestCase has
the same problem (no info for the 'testrl' resource loader).
The ResourceManager code producing that 'no config info' log message is:
String loaderName = (String) it.next();
StringBuffer loaderID = new StringBuffer(loaderName);
loaderID.append(.).append(RuntimeConstants.RESOURCE_LOADER);
ExtendedProperties loaderConfiguration =
rsvc.getConfiguration().subset(loaderID.toString());
if (loaderConfiguration == null)
{
log.debug(ResourceManager : No configuration
information for resource loader named ' +
loaderName + '. Skipping.);
continue;
}
Why this would work for 'file' and not for 'string' or 'testrl' is
currently a baffling mystery to me. My best guess at this point is
that it is due to some underlying change in Commons-Collections'
ExtendedProperties class. But that seems kind of unlikely. Any
insights? I'm about ready to give up and just find a workaround that
makes gump happy, but if there is a bug coming down the line, that
would not be helpful...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
