RFR(XL/M) : 8178788: wrap JCStress test suite as jtreg tests
stuart.monteith at linaro.org
Fri Sep 8 15:53:40 UTC 2017
I've spent some time on this, and I have to admit that I'm stumped. I
get exactly the same errors on x86 on jdk10/hs and jdk10/jdk10 with arecent
build of JTReg and JT_HOME set appropriately.
Are there any pointers on how this is supposed to be run?
On 25 April 2017 at 11:47, Aleksey Shipilev <shade at redhat.com> wrote:
> On 04/19/2017 12:12 AM, Igor Ignatyev wrote:
> > http://cr.openjdk.java.net/~iignatyev//8178788/webrev.00/index.html
> >> 69903 lines changed: 69903 ins; 0 del; 0 mod;
> > (69524 lines are generated)
> > Hi all,
> > could you please review this patch which adds a jtreg test wrapper for
> > jcstress test suite and jtreg tests which run jsctress tests thru this
> > wrapper?
> > webrev: http://cr.openjdk.java.net/~iignatyev//8178788/webrev.00/
> > JBS: https://bugs.openjdk.java.net/browse/JDK-8178788 testing:
> TL;DR: This patch introduces more problems than it solves. Just run the
> tests-all JAR against the tested runtime.
> Wrapping jcstress tests with jtreg defies the purpose of jcstress harness
> that is, running lots of tests as fast as it possibly could without
> testing quality. For example, by cleverly reusing VMs between the tests,
> Whitebox to deoptimize without restarting the VMs, etc. It really wastes
> time to run each test in isolation.
> Also, it does not "automatically" work, which defies "easy to run" goal:
> Caused by: java.io.FileNotFoundException: Couldn't automatically resolve
> dependency for jcstress-tests-all , revision 0.3
> Please specify the location using jdk.test.lib.artifacts.
> at jdk.test.lib.artifacts.ArtifactResolver.resolve(
> at applications.jcstress.JcstressRunner.pathToArtifact(
> ... 8 more
> Okay, brilliant! How do I configure this, if I run "make test"?
> CONF=linux-x86_64-normal-server-release LOG=info make test
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-compiler-dev