JDK-8357785 : [lworld] TestResolvedJavaType fails due to unexpected getInstanceFields order
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: repo-valhalla
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2025-05-26
  • Updated: 2025-07-25
  • Resolved: 2025-07-25
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.
Other
repo-valhallaFixed
Related Reports
Blocks :  
Causes :  
Description
java.lang.AssertionError: ResolvedJavaType.getInstanceFields order differs from Class.getDeclaredFields expected:<HotSpotResolvedJavaFieldImpl<java.util.HashMap$HashIterator.expectedModCount int:12>> but was:<HotSpotResolvedJavaFieldImpl<java.util.HashMap$HashIterator.next HashMap$Node:20>>
	at org.junit.Assert.fail(Assert.java:89)
	at org.junit.Assert.failNotEquals(Assert.java:835)
	at org.junit.Assert.assertEquals(Assert.java:120)
	at jdk.vm.ci.runtime.test.TestResolvedJavaType.getInstanceFieldsTest(TestResolvedJavaType.java:973)
	at java.base/java.lang.reflect.Method.invoke(Method.java:565)
Comments
A pull request was submitted for review. Branch: lworld URL: https://git.openjdk.org/valhalla/pull/1511 Date: 2025-07-17 12:07:56 +0000
17-07-2025