You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jakarta.apache.org by Stefan Bodewig <bo...@apache.org> on 2010/04/22 17:22:06 UTC
[GUMP@vmgump]: Project jakarta-bsf3 (in module jakarta-bsf3) 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 general@gump.apache.org.
Project jakarta-bsf3 has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 284 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- jakarta-bsf3 : Bean Scripting Framework
Full details are available at:
http://vmgump.apache.org/gump/public/jakarta-bsf3/jakarta-bsf3/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were provided:
-INFO- Optional dependency jetty failed with reason build failed
-DEBUG- (Gump generated) Maven2 Settings in: /srv/gump/public/workspace/jakarta-bsf3/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in: /srv/gump/public/workspace/jakarta-bsf3/pom.xml
The following work was performed:
http://vmgump.apache.org/gump/public/jakarta-bsf3/jakarta-bsf3/gump_work/build_jakarta-bsf3_jakarta-bsf3.html
Work Name: build_jakarta-bsf3_jakarta-bsf3 (Type: Build)
Work ended in a state of : Failed
Elapsed: 39 secs
Command Line: mvn --batch-mode --settings /srv/gump/public/workspace/jakarta-bsf3/gump_mvn_settings.xml install
[Working Directory: /srv/gump/public/workspace/jakarta-bsf3]
CLASSPATH: /usr/lib/jvm/java-6-sun/lib/tools.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-apache-xalan2.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/asm/output/dist/lib/all/asm-all-22042010.jar:/srv/gump/public/workspace/asm/output/dist/lib/asm-analysis-22042010.jar:/srv/gump/public/workspace/asm/output/dist/lib/asm-util-22042010.jar:/srv/gump/public/workspace/asm/output/dist/lib/asm-xml-22042010.jar:/srv/gump/public/workspace/asm/output/dist/lib/asm-commons-22042010.jar:/srv/gump/public/workspace/asm/output/
dist/lib/asm-22042010.jar:/srv/gump/public/workspace/asm/output/dist/lib/asm-tree-22042010.jar:/srv/gump/public/workspace/jakarta-bsf3/bsf-api/target/bsf-api-3.0-SNAPSHOT.jar:/srv/gump/public/workspace/commons-collections-3.x/target/commons-collections-3.3-SNAPSHOT.jar:/srv/gump/public/workspace/apache-commons/io/target/commons-io-2.0-SNAPSHOT.jar:/srv/gump/public/workspace/commons-lang-2.x/target/commons-lang-2.6-SNAPSHOT.jar:/srv/gump/public/workspace/groovy/target/groovy-1.8.0-beta-1-SNAPSHOT.jar:/srv/gump/public/workspace/jakarta-oro/jakarta-oro-22042010.jar:/srv/gump/public/workspace/tomcat-tc6/output/build/lib/servlet-api.jar:/srv/gump/public/workspace/jetty/jetty-ajp/target/jetty-ajp-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-plus/target/jetty-plus-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-jndi/target/jetty-jndi-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-deploy/target/jetty-deploy-7.1.0-SNAPSHOT.jar:/srv/gump/public/worksp
ace/jetty/jetty-servlets/target/jetty-servlets-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-servlet/target/jetty-servlet-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-jaspi/target/jetty-jaspi-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-webapp/target/jetty-webapp-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-osgi/jetty-osgi-boot-warurl/target/jetty-osgi-boot-warurl-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-io/target/jetty-io-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-policy/target/jetty-policy-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-security/target/jetty-security-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-server/target/jetty-server-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-http/target/jetty-http-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-osgi/jetty-osgi-boot-jsp/target/jetty-osgi-boot-jsp-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspac
e/jetty/jetty-websocket/target/jetty-websocket-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-continuation/target/jetty-continuation-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-util/target/jetty-util-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-osgi/jetty-osgi-httpservice/target/jetty-httpservice-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-osgi/jetty-osgi-boot-logback/target/jetty-osgi-boot-logback-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-start/target/jetty-start-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-xml/target/jetty-xml-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-osgi/jetty-osgi-boot/target/jetty-osgi-boot-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-jmx/target/jetty-jmx-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-rewrite/target/jetty-rewrite-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/jetty/jetty-client/target/jetty-client-7.1.0-SNAPSHOT.jar:/
srv/gump/public/workspace/jetty/jetty-annotations/target/jetty-annotations-7.1.0-SNAPSHOT.jar:/srv/gump/public/workspace/junit/dist/junit-22042010.jar:/srv/gump/public/workspace/jython/dist/jython-dev.jar:/srv/gump/packages/retroweaver-2.0.7/retroweaver-rt.jar:/srv/gump/packages/retroweaver-2.0.7/retroweaver.jar:/srv/gump/public/workspace/rhino/build/rhino_22042010/js.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-22042010.jar:/srv/gump/public/workspace/velocity-engine/bin/velocity-22042010-dep.jar:/srv/gump/public/workspace/ws-axis2-commons/axiom/modules/axiom-impl/target/axiom-impl-1.2.9-SNAPSHOT.jar:/srv/gump/public/workspace/ws-axis2-commons/axiom/modules/axiom-api/target/axiom-api-1.2.9-SNAPSHOT.jar:/srv/gump/public/workspace/ws-axis2-commons/axiom/modules/axiom-dom/target/axiom-dom-1.2.9-SNAPSHOT.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar
---------------------------------------------
Downloading: http://localhost:8192/maven2/xmlbeans/xbean/2.2.0/xbean-2.2.0.jar
Downloading: http://localhost:8192/maven2/org/codehaus/woodstox/wstx-asl/3.2.0/wstx-asl-3.2.0.jar
Downloading: http://localhost:8192/maven2/org/apache/ws/commons/axiom/axiom-api/1.2.2/axiom-api-1.2.2.jar
Downloading: http://localhost:8192/maven2/jaxen/jaxen/1.1-beta-9/jaxen-1.1-beta-9.jar
Downloading: http://localhost:8192/maven2/rhino/js/1.6R7/js-1.6R7.jar
221K downloaded (jaxen-1.1-beta-9.jar)
384K downloaded (axiom-api-1.2.2.jar)
Downloading: http://localhost:8192/maven2/org/apache/ws/commons/axiom/axiom-impl/1.2.2/axiom-impl-1.2.2.jar
119K downloaded (axiom-impl-1.2.2.jar)
1040K downloaded (js-1.6R7.jar)
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 14 source files to /srv/gump/public/workspace/jakarta-bsf3/bsf-utils/target/classes
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 1 source file to /srv/gump/public/workspace/jakarta-bsf3/bsf-utils/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: /srv/gump/public/workspace/jakarta-bsf3/bsf-utils/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.bsf.xml.JavaScriptXMLHelperTestCase
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.709 sec <<< FAILURE!
Results :
Tests in error:
testToOmElement(org.apache.bsf.xml.JavaScriptXMLHelperTestCase)
testToScriptXML(org.apache.bsf.xml.JavaScriptXMLHelperTestCase)
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
Please refer to /srv/gump/public/workspace/jakarta-bsf3/bsf-utils/target/surefire-reports for the individual test results.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 38 seconds
[INFO] Finished at: Thu Apr 22 07:22:00 PST 2010
[INFO] Final Memory: 27M/48M
[INFO] ------------------------------------------------------------------------
---------------------------------------------
To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/jakarta-bsf3/jakarta-bsf3/rss.xml
- Atom: http://vmgump.apache.org/gump/public/jakarta-bsf3/jakarta-bsf3/atom.xml
============================== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 08000022042010, vmgump:vmgump-public:08000022042010
Gump E-mail Identifier (unique within run) #51.
--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]
Re: Gump nags
Posted by Rahul Akolkar <ra...@gmail.com>.
On Thu, Apr 22, 2010 at 11:39 AM, Stefan Bodewig <bo...@apache.org> wrote:
> On 2010-04-22, Rahul Akolkar <ra...@gmail.com> wrote:
>
>> On Thu, Apr 22, 2010 at 11:29 AM, Stefan Bodewig <bo...@apache.org> wrote:
>>> Hi all,
>
>>> Gump nag mails need to be adjusted so they go to the new list(s) rather
>>> than get re-routed. Do people prefer to have the nag mails go to the
>>> notifications@ list or to dev@?
>
>> Per design, all automated messages should go to notifications@ -- that
>> would include JIRA (already done), SVN commit messages (already done,
>> though may need moderation for each committers first commit), Bugzilla
>> and Gump.
>
> I thought so - and have already changed the Gump descriptors to reflect
> this. As I discovered I am a moderator for both lists so can help with
> moderating through. 8-)
>
<snip/>
Cool, thanks for updating the descriptors and thanks in advance for
the help with moderation.
As a reminder, the progress is being tracked here:
https://issues.apache.org/jira/browse/INFRA-2335
Please add a comment indicating you've updated the Gump descriptors. I
can add the comment too, but you've done the work so I'll leave it to
you :-)
-Rahul
> Stefan
>
Re: Gump nags
Posted by Stefan Bodewig <bo...@apache.org>.
On 2010-04-22, Rahul Akolkar <ra...@gmail.com> wrote:
> On Thu, Apr 22, 2010 at 11:29 AM, Stefan Bodewig <bo...@apache.org> wrote:
>> Hi all,
>> Gump nag mails need to be adjusted so they go to the new list(s) rather
>> than get re-routed. Do people prefer to have the nag mails go to the
>> notifications@ list or to dev@?
> Per design, all automated messages should go to notifications@ -- that
> would include JIRA (already done), SVN commit messages (already done,
> though may need moderation for each committers first commit), Bugzilla
> and Gump.
I thought so - and have already changed the Gump descriptors to reflect
this. As I discovered I am a moderator for both lists so can help with
moderating through. 8-)
Stefan
Re: Gump nags
Posted by Rahul Akolkar <ra...@gmail.com>.
On Fri, Apr 23, 2010 at 11:32 AM, Rahul Akolkar <ra...@gmail.com> wrote:
> On Fri, Apr 23, 2010 at 5:41 AM, Stefan Bodewig <bo...@apache.org> wrote:
>> On 2010-04-22, Rahul Akolkar <ra...@gmail.com> wrote:
>>
>>> Do we have a Bugzilla admin on this list? Atleast the following use
>>> Bugzilla and would need to be updated:
>>
>>> BCEL, BSF, JMeter, ORO, Regexp
>>
>> If notifications@jakarta was the email of a valid Bugzilla user I could
>> modify the products and their compoments to have this as the default
>> owner - and thus the address that gets all notifications. Unfortunately
>> I lack the karma to create new bugzilla users.
>>
> <snip/>
>
> OK, please add a comment to INFRA-2335 indicating what we need (unless
> someone on this list jumps in before that and does the deed).
>
> Currently, Bugzilla notifications are going to dev@ (due to qmail
> redirects) but we should get that changed to notifications@ soon.
>
<snip/>
I've asked for Bugzilla help on the infra list.
-Rahul
Re: Gump nags
Posted by Rahul Akolkar <ra...@gmail.com>.
On Fri, Apr 23, 2010 at 5:41 AM, Stefan Bodewig <bo...@apache.org> wrote:
> On 2010-04-22, Rahul Akolkar <ra...@gmail.com> wrote:
>
>> Do we have a Bugzilla admin on this list? Atleast the following use
>> Bugzilla and would need to be updated:
>
>> BCEL, BSF, JMeter, ORO, Regexp
>
> If notifications@jakarta was the email of a valid Bugzilla user I could
> modify the products and their compoments to have this as the default
> owner - and thus the address that gets all notifications. Unfortunately
> I lack the karma to create new bugzilla users.
>
<snip/>
OK, please add a comment to INFRA-2335 indicating what we need (unless
someone on this list jumps in before that and does the deed).
Currently, Bugzilla notifications are going to dev@ (due to qmail
redirects) but we should get that changed to notifications@ soon.
-Rahul
> Stefan
>
Re: Gump nags
Posted by Stefan Bodewig <bo...@apache.org>.
On 2010-04-22, Rahul Akolkar <ra...@gmail.com> wrote:
> Do we have a Bugzilla admin on this list? Atleast the following use
> Bugzilla and would need to be updated:
> BCEL, BSF, JMeter, ORO, Regexp
If notifications@jakarta was the email of a valid Bugzilla user I could
modify the products and their compoments to have this as the default
owner - and thus the address that gets all notifications. Unfortunately
I lack the karma to create new bugzilla users.
Stefan
Re: Gump nags
Posted by Rahul Akolkar <ra...@gmail.com>.
On Thu, Apr 22, 2010 at 11:29 AM, Stefan Bodewig <bo...@apache.org> wrote:
> Hi all,
>
> Gump nag mails need to be adjusted so they go to the new list(s) rather
> than get re-routed. Do people prefer to have the nag mails go to the
> notifications@ list or to dev@?
>
<snip/>
Thanks, was about to send a similar email :-)
Per design, all automated messages should go to notifications@ -- that
would include JIRA (already done), SVN commit messages (already done,
though may need moderation for each committers first commit), Bugzilla
and Gump.
Do we have a Bugzilla admin on this list? Atleast the following use
Bugzilla and would need to be updated:
BCEL, BSF, JMeter, ORO, Regexp
-Rahul
> Stefan
>
Gump nags
Posted by Stefan Bodewig <bo...@apache.org>.
Hi all,
Gump nag mails need to be adjusted so they go to the new list(s) rather
than get re-routed. Do people prefer to have the nag mails go to the
notifications@ list or to dev@?
Stefan