JDK-8259446 : runtime/jni/checked/TestCheckedReleaseArrayElements.java fails with stderr not empty
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 17
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-01-08
  • Updated: 2021-03-01
  • Resolved: 2021-01-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 11 JDK 16 JDK 17
11.0.11-oracleFixed 16.0.1Fixed 17 b05Fixed
Related Reports
Relates :  
JDK-8258077 - Using -Xcheck:jni can lead to a double-free after JDK-8193234
Description
----------System.err:(25/1261)----------
 stdout: [Array before: [0, 0, 0, 0, 0, 0, 0, 0, 0]
Array during: [0, 1, 2, 0, 0, 0, 0, 0, 0]
Array during: [0, 1, 2, 3, 4, 5, 0, 0, 0]
Array during: [0, 1, 2, 3, 4, 5, 6, 7, 8]
Array after: [0, 1, 2, 3, 4, 5, 6, 7, 8]
];
 stderr: [java version "17-ea" 2021-09-14 LTS
Java(TM) SE Runtime Environment (fastdebug build 17-ea+5-LTS-200)
Java HotSpot(TM) 64-Bit Server VM (fastdebug build 17-ea+5-LTS-200, mixed mode)
]
 exitValue = 0

java.lang.RuntimeException: stderr was not empty
	at jdk.test.lib.process.OutputAnalyzer.stderrShouldBeEmpty(OutputAnalyzer.java:132)
	at TestCheckedReleaseArrayElements.main(TestCheckedReleaseArrayElements.java:52)
Comments
Fix Request (16u) Backporting this low-risk fix prevents this test from failing in JDK-16u. The original bug fix patch applied cleanly. After applying the patch to a JDK-16u repo, the test was run on Linux, Windows, and Mac OS. The test is part of the patch for JDK-8258077.
24-02-2021
Sorry I didn't see Coleen's comment earlier. The fix addresses that issue as well - the test, if accepting external flags would have to use the stderrIsEmptyIgnoreVMWarnings() method.
09-01-2021
Changeset: 7e6677b5 Author: David Holmes <dholmes@openjdk.org> Date: 2021-01-08 22:25:21 +0000 URL: https://git.openjdk.java.net/jdk/commit/7e6677b5
08-01-2021
Oh sorry it was tier3 running tier1 tests.
08-01-2021
[~coleenp] - I don't see any failures in Tier1 in the JDK17 CI...
08-01-2021
I'm seeing this instead. This test shouldn't be in tier1. ----------System.err:(23/1225)---------- stdout: [Array before: [0, 0, 0, 0, 0, 0, 0, 0, 0] Array during: [0, 1, 2, 0, 0, 0, 0, 0, 0] Array during: [0, 1, 2, 3, 4, 5, 0, 0, 0] Array during: [0, 1, 2, 3, 4, 5, 6, 7, 8] Array after: [0, 1, 2, 3, 4, 5, 6, 7, 8] ]; stderr: [Java HotSpot(TM) 64-Bit Server VM warning: Option UseBiasedLocking was deprecated in version 15.0 and will likely be removed in a future release. ] exitValue = 0
08-01-2021
jtreg is being run with: -Dtest.java.opts='-Xshare:off -showversion' which in turn gets passed to the exec'd VM. That extraneous output causes the failure.
08-01-2021