date:20050103

Re: status of xalan breakage?

2005-01-03 Thread Christine Li

Hi,

I investigated the failed gump build for xml-xalan before I went on 
vacation. From the error message, it looks like that there are some 
classpath setting issues. I have no objections to your temporary solution 
and I would like to collaborate to get this problem resolved as a 
developer for xalan. 

I have no problem to build Xalan Head with both Sun JDK1.4.0_03 on 
Windows2000 (and the nightly ant build) as an independent project. Because 
of lack of information about the nightly gump build, I don't know what I 
can do at this moment. 

Would you please let me know how I can reproduce the failed build?
1. version of JDK
2. jar files on the bootclasspath
3. jar files and classes on classpath, etc. 
4. Is there anyway that I can access archive of the gump build?

Any suggestions would be appreciated. Thanks,


Original Message from Brett Porter <[EMAIL PROTECTED]>

>any objections to me doing this?
>
>1) create a xalan-failing project that uses xalan HEAD to build
>2) make the xalan descriptor either package the last release, or build
>from a known-good tag
>3) when xalan-failing starts building again, switch back


Christine Li
XSLT Development
IBM Toronto Lab
Tel: (905)413-2601
Email: [EMAIL PROTECTED]

Problem running Apache Gump [brutus-test]

2005-01-03 Thread brutus

There is a problem with run 'brutus-test' (03012005_091112), location : 
http://brutus.apache.org/gump/test

The log ought be at:
   http://brutus.apache.org/gump/test/gump_log.txt

The last (up to) 50 lines of the log are :
- GUMP run on host   : brutus
- GUMP run @ : 03 Jan 2005 09:11:13
- GUMP run @  UTC: 03 Jan 2005 17:11:13
- GUMP run by Python : '2.3.4 (#2, Sep 24 2004, 08:39:09) \n[GCC 3.3.4 (Debian 
1:3.3.4-12)]'
- GUMP run by Python : '/usr/bin/python2.3'
- GUMP run by Gump   : 2.0.2-alpha-0003
- GUMP run on OS : 'posix'
- GUMP run in env: 
  FORREST_HOME -> [/opt/forrest]
  GUMP_LOG_DIR -> [/usr/local/gump/test/results]
  SSH_CLIENT -> [24.63.102.152 63650 22]
  GUMP_PYTHON -> [/usr/bin/python2.3]
  LOGNAME -> [gump]
  USER -> [gump]
  MAVEN_HOME -> [/opt/maven]
  PATH -> 
[/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/opt/jdk1.4/bin:/opt/forrest/bin:/opt/maven/bin]
  TERM -> [xterm]
  SHELL -> [/bin/bash]
  SHLVL -> [2]
  LOCAL_ENV -> [local-env.sh]
  GUMP -> [/usr/local/gump/test/gump]
  JAVA_HOME -> [/opt/jdk1.4]
  HOME -> [/home/gump]
  HOST_LOCAL_ENV -> [local-env-brutus.sh]
  CLASSPATH -> [/opt/jdk1.4/lib/tools.jar]
  GUMP_HOME -> [/usr/local/gump/test/gump]
  LS_OPTIONS -> [--color=auto]
  _ -> [/usr/bin/python2.3]
  SSH_CONNECTION -> [24.63.102.152 63650 209.237.227.198 22]
  SSH_TTY -> [/dev/pts/1]
  GUMP_HOST -> [brutus]
  PWD -> [/usr/local/gump/test/gump/cron]
  MAIL -> [/var/mail/gump]
  LS_COLORS -> 
[no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.ogg=01;35:*.mp3=01;35:*.wav=01;35:]
  GUMP_WS -> [/usr/local/gump/test/workspace]
- GUMP base directory : /usr/local/gump/test/workspace
- GUMP base path  : /usr/local/gump/test/workspace
- GUMP mail server: mail.apache.org
- GUMP mail port  : 25
- GUMP mail from  : [EMAIL PROTECTED]
- GUMP mail to: general@gump.apache.org
- GUMP log is @   : http://brutus.apache.org/gump/test
- GUMP log is @   : /usr/local/gump/test/results
 - GUMP PYTHONPATH  :  /usr/local/gump/test/gump/python
Terminated by user interrupt...
--
Gump Version: 2.0.2-alpha-0003

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: status of xalan breakage?

2005-01-03 Thread Leo Simons

On 02-01-2005 22:32, "Brett Porter" <[EMAIL PROTECTED]> wrote:
> any objections to me doing this?

Not from me!

- Leo

> 1) create a xalan-failing project that uses xalan HEAD to build
> 2) make the xalan descriptor either package the last release, or build
> from a known-good tag
> 3) when xalan-failing starts building again, switch back



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

BATCH: All dressed up, with nowhere to go...

2005-01-03 Thread brutus

Dear Gumpmeisters,

The following 7 notifys should have been sent

*** G U M P
[EMAIL PROTECTED]: Module lenya success, but with warnings.
[EMAIL PROTECTED]: Project nant (in module nant) failed
[EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) 
success, but with warnings.
[EMAIL PROTECTED]: Module struts success, but with warnings.
[EMAIL PROTECTED]: Project asm (in module asm) failed
[EMAIL PROTECTED]: Project jtidy-cvs (in module jtidy) failed
[EMAIL PROTECTED]: Project JacORB (in module JacORB) failed
*** G U M P
[EMAIL PROTECTED]: Module lenya success, but with warnings.
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]

Module lenya contains errors.
The current state of this module is 'Success'.

Full details are available at:
http://brutus.apache.org/gump/public/lenya/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -ERROR- *** Failed to update from source control. Stale contents ***



The following work was performed:
http://brutus.apache.org/gump/public/lenya/gump_work/update_lenya.html
Work Name: update_lenya (Type: Update)
Work ended in a state of : Failed
Elapsed: 55 secs
Command Line: svn --quiet update --non-interactive lenya 
[Working Directory: /usr/local/gump/public/workspace/cvs]
-
svn: Working copy 'lenya/src/webapp/lenya/resources/bxe/plugins' not locked
-

To subscribe to this information via syndicated feeds:
- RSS: http://brutus.apache.org/gump/public/lenya/rss.xml
- Atom: http://brutus.apache.org/gump/public/lenya/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2703012005, brutus:brutus-public:2703012005
Gump E-mail Identifier (unique within run) #1.

*** G U M P
[EMAIL PROTECTED]: Project nant (in module nant) 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 nant has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 36 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- nant :  NAnt is a free .NET build tool. In theory it is kind of like...


Full details are available at:
http://brutus.apache.org/gump/public/nant/nant/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://brutus.apache.org/gump/public/nant/nant/gump_work/build_nant_nant.html
Work Name: build_nant_nant (Type: Build)
Work ended in a state of : Failed
Elapsed: 4 secs
Command Line: make 
[Working Directory: /usr/local/gump/public/workspace/nant]
-
mono bin/NAnt.exe -f:NAnt.build build
Compat mode: the request from 
/home/gump/workspaces2/public/workspace/nant/bin/log4net.dll to load System was 
remapped (http://www.go-mono.com/remap.html)
Compat mode: the request from 
/home/gump/workspaces2/public/workspace/nant/bin/log4net.dll to load 
System.Data was remapped (http://www.go-mono.com/remap.html)
Compat mode: the request from 
/home/gump/workspaces2/public/workspace/nant/bin/log4net.dll to load System.Web 
was remapped (http://www.go-mono.com/remap.html)
NAnt 0.85 (Build 0.85.1812.0; dev; 12/17/2004)
Copyright (C) 2001-2004 Gerry Shaw
http://nant.sourceforge.net


BUILD FAILED

The current runtime framework 'mono-1.0' is not correctly configured in the 
NAnt configuration file.
Unable to locate 'mono' module using pkg-config. Download the Mono 
development packages from http://www.mono-project.com/downloads/.

For more information regarding the cause of the build failure, run the build 
again in debug mode.

Try 'nant -help' for more information
make: *** [build-nant] Error 1
-

To subscribe to this information via syndicated feeds:
- RSS: http://brutus.apache.org/gump/public/nant/nant/rss.xml
- Atom: http://brutus.apache.org/gump/public/nant/nant/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 2703012005, brutus:brutus-public:2703012005
Gump E-mail Identifier (unique within run) #2.

**

Re: status of xalan breakage?

Problem running Apache Gump [brutus-test]

Re: status of xalan breakage?

BATCH: All dressed up, with nowhere to go...

4 matches

Site Navigation

Mail list logo

Footer information