skip jcstress tests when running jtreg
Roman Kennke
rkennke at redhat.com
Tue Jul 18 15:24:54 UTC 2017
+1!
I'd just run upstream jcstress instead and avoid the problematic
jcstress stuff in jtreg.
Roman
Am 18.07.2017 um 17:21 schrieb Lindenmaier, Goetz:
>
> Hi Igor,
>
>
>
> We used to execute all jtreg tests via group hotspot_all.
>
> Since the jcstress tests were submitted we run into timeouts
>
> and other problems.
>
>
>
> We would like to run all tests but the jcstress tests, and
>
> then run the jcstress tests in a run of its own.
>
> Unfortunately, we didn’t find a good way to exclude them.
>
>
>
> It seems not to work to add
>
> applications/jcstress/acqrel/Test.java generic-all
>
> to the ProblemList.txt.
>
> There is no specific group in TEST.groups.
>
> Also, there is no keyword associated with the tests.
>
>
>
> Is there a way to exclude these but run all others I oversaw?
>
> Would it make sense to add @key stress to all the jcstress tests?
>
> Should we add a group hotspot_all_no_jcstress or the like to TEST.groups?
>
>
>
> Best regards,
>
> Goetz.
>
>
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/attachments/20170718/084878ad/attachment.html>
More information about the hotspot-compiler-dev
mailing list