JDK-8268227 : java/foreign/TestUpcall.java still times out
  • Type: Bug
  • Component: core-libs
  • Affected Version: 17
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux
  • CPU: x86_64
  • Submitted: 2021-06-04
  • Updated: 2021-06-11
  • Resolved: 2021-06-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 17
17 b26Fixed
Related Reports
Relates :  
JDK-8266074 - Vtable-based CHA implementation
Relates :  
JDK-8268131 - 2 java/foreign tests timed out
Description
The following test still times out after JDK-8268131:

java/foreign/TestUpcall.java

so it looks like (4 minutes * 4 timeoutFactor) => 16 minutes
isn't enough.
Comments
The fix for this bug is in jdk-17+26-2364 and jdk-17+26-2365. So even though there's a sighting in jdk-17+26-2356-tier4, that build-ID DOES NOT have the fix.
08-06-2021
Changeset: 6843576c Author: Maurizio Cimadamore <mcimadamore@openjdk.org> Date: 2021-06-08 14:02:28 +0000 URL: https://git.openjdk.java.net/jdk/commit/6843576c95a70bffad95df278d5f5be29371bca4
08-06-2021
Ultimately, it seems like this is likely caused by this: https://bugs.openjdk.java.net/browse/JDK-8268095 Adding -XX:-VerifyDependencies to these tests make everything complete in a minute or so. I'm discussing this with HS team to see if there's a workaround we can use - bumping timeout doesn't seem optimal as it will leave the test running for a very long time.
04-06-2021
[~mcimadamore] - Looks like java/foreign/TestUpcall.java needs more time.
04-06-2021