Community
Participate
Working Groups
In a recent build we had failures in these tests: org.eclipse.objectteams.otdt.tests.superhierarchy.OTSuperTypeHierarchyTest001.testGetAllSuperclasses_T8R2_phantomMode org.eclipse.objectteams.otdt.tests.superhierarchy.OTSuperTypeHierarchyTest001.testGetAllSuperclasses_T7R3_phantomMode org.eclipse.objectteams.otdt.tests.superhierarchy.OTSuperTypeHierarchyTest001.testGetAllSuperclasses_T7R2_phantomMode org.eclipse.objectteams.otdt.tests.superhierarchy.OTSuperTypeHierarchyTest001.testGetAllSuperclasses_T4R2_phantomMode org.eclipse.objectteams.otdt.tests.superhierarchy.OTSuperTypeHierarchyTest001.testLinearizationR2 org.eclipse.objectteams.otdt.tests.superhierarchy.OTSuperTypeHierarchyTest006.testGetAllSuperclasses_T3R2_phantomMode When investigating when this was introduced I wasn't even able to reproduce a clean test run using a recent release version, so I assume that the failures depend on some implicit processing-order issue?
Created attachment 206073 [details] fix This check in HierarchyResolver was too narrow, thus no OTType was registered for phantom role T7.R1. Inspecting the file history showed that this change was introduced way back during the migration to Eclipse 3.2 to accommodate changed processing order in 3.2, but the condition in question was not further documented.
Released for 2.1 M3 (r2074).
The fix has been backported to 2.0.2 via commit 8ad00e64e1caa6f90336b7a9594f5694c29ac893
Tests are green, considering as fixed indeed.