You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by "Adam R. B. Jack" <aj...@trysybase.com> on 2003/10/27 17:26:42 UTC

Verification help please...

I was struggling with a recursive algorithm to build the CLASSPATH because
of inherit. (Ought I follow what is on this depend, or what is on the
project? Do I follow 'runtime' despite inherit, or in conjunction with,
etc.) I persuaded myself of a number of permutations, none of which were
correct -- until I finally arrived where I am now. I think the answer to the
first is 'both', and (especially now I separate out/set the bootclasspath)
the results appear to bear that out.

http://lsd.student.utwente.nl/gump/index.html
http://lsd.student.utwente.nl/gump/todos.html

Most of these look 'correct', i.e. issues that the teams would resolve if we
could/would nag them. That said, despite 163 successes, there are 228 not
attempted due to pre-requisite failures (on LSD). Maybe those would uncover
combinations of dependencies that would break the logic, I can't tell.

Projects | Successes | Failures | Prereqs | No Works | Packages
512       |  163          | 25         | 228      | 56              | 40

I see some odd things (almost every run) but then almost every run is
different (not just my changes) so I've not been able to put my finger on
anything. I tried to compare to gump.covalent.com/log, but with different
times of run, I'm sometimes comparing apples and oranges. I need to find a
way to determine if there are any other subtle differences that I'm missing.

I feel that results on LSD differ from results on dotnot.org, especially
w.r.t XALAN. Xalan causes a lot of things not to build. (See:
http://lsd.student.utwente.nl/gump/xml-xalan/xml-xalan2.html)

What are folks thoughts on how I verify that  the Gump logic is now complete
and correct? What are folks thoughts on how I verify that the environment
Gump runs in/produces is now complete and correct?

Thanks in advance for any help.

regards,

Adam
--
Experience Sybase Technology...
http://www.try.sybase.com


Re: Verification help please...

Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
Thanks Leo, this is really helpful. I'd considered classpath & commandline,
and general env, but not this (in hindsight obvious) difference. I'm going
to make 'JDK version' much more prominent on the main page, so external
users know what was used, and I'll explore this angle.

regards

Adam
----- Original Message ----- 
From: "Leo Simons" <le...@apache.org>
To: <gu...@jakarta.apache.org>
Sent: Monday, October 27, 2003 3:38 PM
Subject: Re: Verification help please...


> Adam R. B. Jack wrote:
> > I feel that results on LSD differ from results on dotnot.org, especially
> > w.r.t XALAN. Xalan causes a lot of things not to build. (See:
> > http://lsd.student.utwente.nl/gump/xml-xalan/xml-xalan2.html)
>
> compare:
>
>
http://lsd.student.utwente.nl/gump/xml-xalan/build/build_xml-xalan_xml-xalan2.html
>
> has these:
>      [javac] Note: Some input files use or override a deprecated API.
>      [javac] Note: Recompile with -deprecation for details.
>
> http://gump.covalent.com/log/xml-xalan2.html
>
> doesn't. I'm guessing this has to do with LSD having a more recent jdk,
> which might have a bug or be more strict in some way. Maybe using an
> older jdk (I think I have several installed) would work.
>
> > What are folks thoughts on how I verify that the Gump logic is now
complete
> > and correct? What are folks thoughts on how I verify that the
environment
> > Gump runs in/produces is now complete and correct?
>
> difficult questions! One thing we could do is (perhaps manually) parse
> the build.sh/gen.sh that traditional gump generates and compare it to
> the stuff gumpy produces. I guess that they should be functionally
> equivalent....lets dig a little....
>
> ssh lsd
> cd /data/gump/jakarta-gump
> sh gen.sh
>
> Checking for local dependencies in lsd.xml
>
> Unexpected failure in LocalCheck
> java.lang.Exception: workspace version 0.3 required.
>          at Workspace.init(Workspace.java:169)
>          at LocalCheck.<init>(LocalCheck.java:100)
>          at LocalCheck.main(LocalCheck.java:222)
>
> *** FAILED ***
>
> (change version to 0.3; retry; it works)
>
> grep -A 20 'if test \$xml_xalan2;' build.sh | less
>
> test -d /data/gump/xml-xalan || cp -r /data/gump/cvs/xml-xalan
> /data/gump/xml-xalan
> eval "cd /data/gump/xml-xalan $OUT 2>&1"
> export CLASSPATH=$CP:$JAVA_HOME/lib/tools.jar
> export CLASSPATH=$CLASSPATH:/data/gump/log/jars/ant/ant.jar
> export CLASSPATH=$CLASSPATH:/data/gump/log/jars/ant/ant-launcher.jar
> export CLASSPATH=/data/gump/log/jars/xml-xerces2/xercesImpl.jar:$CLASSPATH
> export
> CLASSPATH=/data/gump/log/jars/xml-xerces2/xmlParserAPIs.jar:$CLASSPATH
> export CLASSPATH=$CLASSPATH:/data/gump/xml-xalan/java/bin/java_cup.jar
> export CLASSPATH=$CLASSPATH:/data/gump/xml-xalan/java/bin/runtime.jar
> export CLASSPATH=$CLASSPATH:/data/gump/xml-xalan/java/bin/JLex.jar
> export CLASSPATH=$CLASSPATH:/data/gump/log/jars/jakarta-bcel/bcel.jar
> export CLASSPATH=/data/gump/log/jars/xml-commons/xml-apis.jar:$CLASSPATH
> export CLASSPATH=$CLASSPATH:/data/gump/xml-xalan/java/build/classes
> eval "cd /data/gump/xml-xalan/java $OUT 2>&1"
> if test "$STATUS" = "SUCCESS"; then \
> eval "java
> -Xbootclasspath/p:/data/gump/log/jars/xml-xerces2/xercesImpl.jar:/data/gum
p/log/jars/xml-xerces2/xmlParserAPIs.jar
> :/data/gump/log/jars/xml-commons/xml-apis.jar org.apache.tools.ant.Main
> -Dbuild.sysclasspath=only -Dbcel.jar=/data/gump/jakar
> ta-bcel/bin/bcel.jar $TARGET </dev/null $OUT 2>&1"
>
> which should equal
>
> cd /data/gump/xml-xalan/java
> export CLASSPATH=/data/gump/log/jars/xml-commons/xml-apis.jar: \
>   /data/gump/log/jars/xml-xerces2/xmlParserAPIs.jar: \
>   /data/gump/log/jars/xml-xerces2/xercesImpl.jar \
>   :$CLASSPATH:$CP:$JAVA_HOME/lib/tools.jar: \
>   /data/gump/log/jars/ant/ant.jar: \
>   /data/gump/log/jars/ant/ant-launcher.jar: \
>   /data/gump/xml-xalan/java/bin/java_cup.jar: \
>   /data/gump/xml-xalan/java/bin/runtime.jar: \
>   /data/gump/xml-xalan/java/bin/JLex.jar: \
>   /data/gump/xml-xalan/java/build/classes
>
> java \
>   -Xbootclasspath/p:/data/gump/log/jars/xml-xerces2/xercesImpl.jar: \
>   /data/gump/log/jars/xml-xerces2/xmlParserAPIs.jar \
>   :/data/gump/log/jars/xml-commons/xml-apis.jar \
>   org.apache.tools.ant.Main -Dbuild.sysclasspath=only \
>   -Dbcel.jar=/data/gump/jakarta-bcel/bin/bcel.jar \
>   $TARGET < /dev/null 2>&1 >> xml-xalan-build.log
>
> (or, without formatting (easy cut-n-paste)):
>
> export
>
CLASSPATH=/data/gump/log/jars/xml-commons/xml-apis.jar:/data/gump/log/jars/x
ml-xerces2/xmlParserAPIs.jar:/data/gump/log/jars/xml-xerces2/xercesImpl.jar:
$CLASSPATH:$CP:$JAVA_HOME/lib/tools.jar:/data/gump/log/jars/ant/ant.jar:/dat
a/gump/log/jars/ant/ant-launcher.jar:/data/gump/xml-xalan/java/bin/java_cup.
jar:/data/gump/xml-xalan/java/bin/runtime.jar:/data/gump/xml-xalan/java/bin/
JLex.jar:/data/gump/xml-xalan/java/build/classes
>
> java
> -Xbootclasspath/p:/data/gump/log/jars/xml-xerces2/xercesImpl.jar:/data/gum
p/log/jars/xml-xerces2/xmlParserAPIs.jar:/data/gump/log/jars/xml-commons/xml
-apis.jar
> org.apache.tools.ant.Main -Dbuild.sysclasspath=only
> -Dbcel.jar=/data/gump/jakarta-bcel/bin/bcel.jar unbundledjar < /dev/null
> 2>&1 >> xml-xalan-build.log
>
> this leads to the exact same error gumpy spits out at me. Which is
> generally a good thing. Let's change the jdk...
>
> export JAVA_HOME=/opt/ibmjdk
> export PATH=/opt/ibmjdk/bin:$PATH
> java -version
> java version "1.3.1"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1)
> Classic VM (build 1.3.1, J2RE 1.3.1 IBM build cxia32131-20020302 (JIT
> enabled: jitc))
>
> (re-run generation, re-run commands; this time lazyly using 'build
> xml-xerces')
>
> guess what? Same error!
>
> cd /data/gump/xml-xerces/java
> rm -Rf java
> cvs -z3 up -Pd
>
> (re-gen, switching back to jdk 1.4)
>
> guess what? It works! Well, almost; it gets up to
>
> xsltc.compile:
>       [echo] Compiling remaining XSLTC classes
>      [javac] Compiling 277 source files to
> /data/gump/xml-xalan/java/build/classes
>      [javac]
>
/data/gump/xml-xalan/java/src/org/apache/xalan/xsltc/compiler/AbsoluteLocati
onPath.java:66:
> package org.apache.bcel.generic does not exist
>      [javac] import org.apache.bcel.generic.ConstantPoolGen;
>
> at this point, I don't feel like more digging. So I've done
>
> cd /data/gump/cvs/xml-xerces/java
> rm -Rf java
> cvs -z3 up -Pd
> cd cvs/jakarta-gump/
> cd /data/gump/cvs/jakarta-gump
> rm -Rf lsd* rm -Rf project/*
> cvs -z3 up -Pd
>
> as well; we'll see what happens.
>
> It might also be a good idea to run the traditional gump on lsd as well
> a few times. I can look into scheduling it to run right after gumpy or
> something like that. More later.
>
> g'night!
>
> - Leo
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: gump-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: gump-help@jakarta.apache.org
>


Re: Verification help please...

Posted by Leo Simons <le...@apache.org>.
Adam R. B. Jack wrote:
> I feel that results on LSD differ from results on dotnot.org, especially
> w.r.t XALAN. Xalan causes a lot of things not to build. (See:
> http://lsd.student.utwente.nl/gump/xml-xalan/xml-xalan2.html)

compare:

http://lsd.student.utwente.nl/gump/xml-xalan/build/build_xml-xalan_xml-xalan2.html

has these:
     [javac] Note: Some input files use or override a deprecated API.
     [javac] Note: Recompile with -deprecation for details.

http://gump.covalent.com/log/xml-xalan2.html

doesn't. I'm guessing this has to do with LSD having a more recent jdk, 
which might have a bug or be more strict in some way. Maybe using an 
older jdk (I think I have several installed) would work.

> What are folks thoughts on how I verify that the Gump logic is now complete
> and correct? What are folks thoughts on how I verify that the environment
> Gump runs in/produces is now complete and correct?

difficult questions! One thing we could do is (perhaps manually) parse 
the build.sh/gen.sh that traditional gump generates and compare it to 
the stuff gumpy produces. I guess that they should be functionally 
equivalent....lets dig a little....

ssh lsd
cd /data/gump/jakarta-gump
sh gen.sh

Checking for local dependencies in lsd.xml

Unexpected failure in LocalCheck
java.lang.Exception: workspace version 0.3 required.
         at Workspace.init(Workspace.java:169)
         at LocalCheck.<init>(LocalCheck.java:100)
         at LocalCheck.main(LocalCheck.java:222)

*** FAILED ***

(change version to 0.3; retry; it works)

grep -A 20 'if test \$xml_xalan2;' build.sh | less

test -d /data/gump/xml-xalan || cp -r /data/gump/cvs/xml-xalan 
/data/gump/xml-xalan
eval "cd /data/gump/xml-xalan $OUT 2>&1"
export CLASSPATH=$CP:$JAVA_HOME/lib/tools.jar
export CLASSPATH=$CLASSPATH:/data/gump/log/jars/ant/ant.jar
export CLASSPATH=$CLASSPATH:/data/gump/log/jars/ant/ant-launcher.jar
export CLASSPATH=/data/gump/log/jars/xml-xerces2/xercesImpl.jar:$CLASSPATH
export 
CLASSPATH=/data/gump/log/jars/xml-xerces2/xmlParserAPIs.jar:$CLASSPATH
export CLASSPATH=$CLASSPATH:/data/gump/xml-xalan/java/bin/java_cup.jar
export CLASSPATH=$CLASSPATH:/data/gump/xml-xalan/java/bin/runtime.jar
export CLASSPATH=$CLASSPATH:/data/gump/xml-xalan/java/bin/JLex.jar
export CLASSPATH=$CLASSPATH:/data/gump/log/jars/jakarta-bcel/bcel.jar
export CLASSPATH=/data/gump/log/jars/xml-commons/xml-apis.jar:$CLASSPATH
export CLASSPATH=$CLASSPATH:/data/gump/xml-xalan/java/build/classes
eval "cd /data/gump/xml-xalan/java $OUT 2>&1"
if test "$STATUS" = "SUCCESS"; then \
eval "java 
-Xbootclasspath/p:/data/gump/log/jars/xml-xerces2/xercesImpl.jar:/data/gump/log/jars/xml-xerces2/xmlParserAPIs.jar
:/data/gump/log/jars/xml-commons/xml-apis.jar org.apache.tools.ant.Main 
-Dbuild.sysclasspath=only -Dbcel.jar=/data/gump/jakar
ta-bcel/bin/bcel.jar $TARGET </dev/null $OUT 2>&1"

which should equal

cd /data/gump/xml-xalan/java
export CLASSPATH=/data/gump/log/jars/xml-commons/xml-apis.jar: \
  /data/gump/log/jars/xml-xerces2/xmlParserAPIs.jar: \
  /data/gump/log/jars/xml-xerces2/xercesImpl.jar \
  :$CLASSPATH:$CP:$JAVA_HOME/lib/tools.jar: \
  /data/gump/log/jars/ant/ant.jar: \
  /data/gump/log/jars/ant/ant-launcher.jar: \
  /data/gump/xml-xalan/java/bin/java_cup.jar: \
  /data/gump/xml-xalan/java/bin/runtime.jar: \
  /data/gump/xml-xalan/java/bin/JLex.jar: \
  /data/gump/xml-xalan/java/build/classes

java \
  -Xbootclasspath/p:/data/gump/log/jars/xml-xerces2/xercesImpl.jar: \
  /data/gump/log/jars/xml-xerces2/xmlParserAPIs.jar \
  :/data/gump/log/jars/xml-commons/xml-apis.jar \
  org.apache.tools.ant.Main -Dbuild.sysclasspath=only \
  -Dbcel.jar=/data/gump/jakarta-bcel/bin/bcel.jar \
  $TARGET < /dev/null 2>&1 >> xml-xalan-build.log

(or, without formatting (easy cut-n-paste)):

export 
CLASSPATH=/data/gump/log/jars/xml-commons/xml-apis.jar:/data/gump/log/jars/xml-xerces2/xmlParserAPIs.jar:/data/gump/log/jars/xml-xerces2/xercesImpl.jar:$CLASSPATH:$CP:$JAVA_HOME/lib/tools.jar:/data/gump/log/jars/ant/ant.jar:/data/gump/log/jars/ant/ant-launcher.jar:/data/gump/xml-xalan/java/bin/java_cup.jar:/data/gump/xml-xalan/java/bin/runtime.jar:/data/gump/xml-xalan/java/bin/JLex.jar:/data/gump/xml-xalan/java/build/classes

java 
-Xbootclasspath/p:/data/gump/log/jars/xml-xerces2/xercesImpl.jar:/data/gump/log/jars/xml-xerces2/xmlParserAPIs.jar:/data/gump/log/jars/xml-commons/xml-apis.jar 
org.apache.tools.ant.Main -Dbuild.sysclasspath=only 
-Dbcel.jar=/data/gump/jakarta-bcel/bin/bcel.jar unbundledjar < /dev/null 
2>&1 >> xml-xalan-build.log

this leads to the exact same error gumpy spits out at me. Which is 
generally a good thing. Let's change the jdk...

export JAVA_HOME=/opt/ibmjdk
export PATH=/opt/ibmjdk/bin:$PATH
java -version
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1)
Classic VM (build 1.3.1, J2RE 1.3.1 IBM build cxia32131-20020302 (JIT 
enabled: jitc))

(re-run generation, re-run commands; this time lazyly using 'build 
xml-xerces')

guess what? Same error!

cd /data/gump/xml-xerces/java
rm -Rf java
cvs -z3 up -Pd

(re-gen, switching back to jdk 1.4)

guess what? It works! Well, almost; it gets up to

xsltc.compile:
      [echo] Compiling remaining XSLTC classes
     [javac] Compiling 277 source files to 
/data/gump/xml-xalan/java/build/classes
     [javac] 
/data/gump/xml-xalan/java/src/org/apache/xalan/xsltc/compiler/AbsoluteLocationPath.java:66: 
package org.apache.bcel.generic does not exist
     [javac] import org.apache.bcel.generic.ConstantPoolGen;

at this point, I don't feel like more digging. So I've done

cd /data/gump/cvs/xml-xerces/java
rm -Rf java
cvs -z3 up -Pd
cd cvs/jakarta-gump/
cd /data/gump/cvs/jakarta-gump
rm -Rf lsd* rm -Rf project/*
cvs -z3 up -Pd

as well; we'll see what happens.

It might also be a good idea to run the traditional gump on lsd as well 
a few times. I can look into scheduling it to run right after gumpy or 
something like that. More later.

g'night!

- Leo