jcstress tests

[Johnson, Andy]

We are running with a build based on jdk8u60.  I notice that tests-all reports that there are 6070 tests, but that 926 of them report "Sanity check failed, API mismatch?", so only 5144 tests are actually run.  Is this intentional?  I know that the tests must be built with jdk-9 build 127 or later, but I was under the impression that the tests would run with any jdk-8 build.  I didn't realize that so many tests would be skipped, due to class versioning errors.  Is there a way to modify the build process so that the results of the build are class version 52, or are these 926 tests really intended for jdk-9 builds only?

-AndyJ

-----Original Message-----
From: Aleksey Shipilev [mailto:aleksey.shipilev at gmail.com] 
Sent: Saturday, August 13, 2016 12:32 PM
To: Johnson, Andy <johnsona at cboe.com>; jcstress-dev at openjdk.java.net
Subject: Re: jcstress tests

On 08/13/2016 08:24 PM, Johnson, Andy wrote:
> Have tests been deleted, restructured, or do they now live somewhere 
> else.

Many tests in suite are auto-generated. We have pruned are restructured test generators a lot over the few previous months.

> I notice that there are a lot more jcstress.jar files than from 
> earlier builds.  Do these now have to be run separately, even though 
> they were created as part of a tests-all build?

test-chapter-* subprojects usually focus on a particular language/library feature now. They can be run separately.

tests-all, like before, merges all subprojects into one big fat JAR. So, if you want to run the entire suite, you can run tests-all/target/jcstress.jar.

Thanks,
-Aleksey