Re: [rvm-research] Exception while executing Junit Test Cases while running pre-commit

Hi,

On 28.04.2013 20:51, Pushparaj Motamari wrote:
> I try to reserve one extra localWords for storing "this" reference. I
> have added some extra check in some methods as suggested by Michel Bond,
> and the precommit went successful for prototype but when I run precommit
> for developement configuration, by the command
> bin/buildit --test-run pre-commit --java-home /usr/local/jdk1.6.0_37
> localhost development
> some tests were failed, I am attaching the build-test results when
> precommit is run for development configuration.

I suggest that you ensure that your changes are correct for the baseline
compiler before attempting to modify the optimizing compiler.

You can check if the problems also occur with the baseline compiler by
running the dacapo benchmarks on the prototype configuration manually or
by defining a suitably changed test-run (see build/test-runs/ for the
currently defined ones).

> I have changed following files in Jikes RVM

IMHO it's best to provide a single patch file if you want someone else
to look at your changes. The patch should use the unified diff format or
the git diff format. If you're using the diff command, you can use the
-u flag to switch on unified diffs. In case you're using Mercurial for
managing your changes, you can also use the hg diff command (if the
changes are uncommitted) or the hg export command (if the changes are in
committed revisions) to produce a suitable patch.


Kind regards,

Erik Brangs

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr