From jvanek at openjdk.org Fri Jul 4 16:11:51 2025 From: jvanek at openjdk.org (=?UTF-8?B?SmnFmcOt?= =?UTF-8?B?IA==?= =?UTF-8?B?VmFuxJtr?=) Date: Fri, 4 Jul 2025 16:11:51 GMT Subject: RFR: 7903671: jcstress: Update buffer tests for JDK-8318966 [v2] In-Reply-To: <7jEnxypEu_yR5K5z69iH3bAZ9DGBxUxXXNhFfe_c6BQ=.8ed3d526-579b-449a-9216-de5827e81072@github.com> References: <7jEnxypEu_yR5K5z69iH3bAZ9DGBxUxXXNhFfe_c6BQ=.8ed3d526-579b-449a-9216-de5827e81072@github.com> Message-ID: On Fri, 6 Jun 2025 15:00:43 GMT, Aleksey Shipilev wrote: > Finally have time to look at this. > > No, we are not going to hard-code test names in generic harness code. The common way to "skip" the test that are incompatible with some JDKs is to record them as "soft errors", which make them skipped. This is what [CODETOOLS-7903695](https://bugs.openjdk.org/browse/CODETOOLS-7903695) did, and it is supposed to be enough. > Ok. you are right. They are just api-mishmash, so soft errors, so ignored. Not sure when I run it last so it was so intrusive it led me to create and elaborate on CODETOOLS-7903671. That sounds like this PR is indeed no go. I'm tempted to add the `alignment(1)` variants so jdk24+ do not suffer the lack of coverage. What is your advice here? ------------- PR Comment: https://git.openjdk.org/jcstress/pull/159#issuecomment-3036788607