Re: [Jikesrvm-researchers] running Mauve with JikesRVM(+GNU Classpath)

Re: [Jikesrvm-researchers] running Mauve with JikesRVM(+GNU Classpath)

[Raif S. Naffah]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

hello David,

On Mon, 7 Apr 2003 09:41 pm, David P Grove wrote:
> Hi,
>
>         I usually do the following for your step 3 (assuming you want
> to test the glib.zip in the JikesRVM build directory. BTW, for
> historical reasons glib.zip is copied into the build directory and
> renamed to rvmrt.jar by the JikesRVM build process).
>
> $ JAVAC="$RVM_BUILD/jbuild.tool" \
>   JAVA="rvm -X:h=100" \
>   ../mauve/configure
>
> jbuild.tool is a script that invokes jikes passing it a bootclasspath
> that includes all the .jar and .classes of the Jikes RVM build
> directory. Jikes RVM's classpath includes the jar files in the build
> directory automatically, so you don't have to specify that.

thanks a bunch :-)

cheers;
rsn


> --dave
>
> "Raif S. Naffah" <raif@fl.net.au>
> Sent by: jikesrvm-researchers-admin@www-124.southbury.usf.ibm.com
> 04/06/2003 08:56 PM
> Please respond to jikesrvm-researchers
>
>         To:     GNU Classpath <classpath@gnu.org>, JikesRVM
> <jikesrvm-researchers@www-124.southbury.usf.ibm.com>, Mauve
> <mauve-discuss@sources.redhat.com>
>         cc:
>         Subject:        [Jikesrvm-researchers] running Mauve with
> JikesRVM(+GNU Classpath)
>
>
> hello there,
>
> if somebody is using the above combo to test GNU Classpath and
> security classes, can they confirm this (how-to-do):
>
> 1. build JikesRVM.  which may download the Classpath CVS HEADs.
> 2. cd to the MAUVE test directory; eg. .../mauve-test
> 3. do:
> $ JAVAC="jikes -bootclasspath <path/to/glibj.zip>" \
>   JAVA="rvm
> -X:vmClasses=<path/to/glibj.zip>:<$RVM_BUILD/RVM.classes>" \
> ../mauve/configure
>
> (unless there's an easier way)
>
> 4. do:
> $rm -rf .save-keys choices ; \
>   make check KEYS="security" TESTFLAGS="-verbose -debug"
>
> where a mauve-security contains something like:
>
> JDK1.0
> JDK1.1
> JDK1.2
> JDK1.3
> JDK1.4
>
> !java.applet
> !java.awt
> !java.beans
> !java.io
> !java.lang
> !java.math
> !java.net
> !java.nio
> !java.rmi
> java.security
> !java.sql
> !java.text
> !java.util
>
> !javax.
>
> 5. the result should be (as of today):
>    0 of 164 tests failed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Que du magnifique

iD8DBQE+kWfA+e1AKnsTRiERA4+1AJ9dtUUwqUtVNokNj8E8Ntb2gx6KwgCg8Gao
uYxeTt7f/kZNOIB8kbPayNU=
=asiF
-----END PGP SIGNATURE-----

Re: [Jikesrvm-researchers] running Mauve with JikesRVM(+GNU Classpath)

[Raif S. Naffah]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

On Monday 07 April 2003 11:25, Michael Hind wrote:
> ...
> We run the mauve tests on Jikes RVM+Classpath head nightly and
> automatically  post the results on the jikesrvm-regression list,
> which is archived at
>         http://www-124.ibm.com/pipermail/jikesrvm-regression
>
> The results from Saturday night can be found here
>
> http://www-124.ibm.com/pipermail/jikesrvm-regression/2003-April/00184
>3.html

noted.

i'm more interested in coming up with a way of testing patches, and 
modifications to GNU Classpath _before_ checking them in.

as you may have noticed, the included (my) how-to is not very reliable, 
since it depends on a build+install of GNU Classpath, before building 
JikesRVM.  the ideal is to let a launcher use the .classes generated by 
JikesRVM jbuild script if possible.


> It appears that the security tests were run and there were no
> failures.

thanks for your prompt reply + cheers;
rsn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Que du magnifique

iD8DBQE+kNsi+e1AKnsTRiERA1l7AJ9cjVgqFIIX1LQ+lMSlHuHSbaxGmwCg29Xb
c9c3AjExqbCCMjvXe4Lg08o=
=uEUR
-----END PGP SIGNATURE-----