Community
Participate
Working Groups
If you use -Dordering=3 system property to change tests order while running JUnit JDT/Core all tests, then some tests are failing and model tests do not finish. The "ordering" system property specified in launch configuration VM arguments change tests order in following manner: 1: alphabetical ascending order 2: alphabetical descending order 3: random order using JDT/Core version for seed 4: random order using time for seed n: random order using given 'n' value for seed This option simulates a VM which would sort methods differently than usual ones...
Created attachment 43863 [details] Failing tests using Sun 1.5.0_08 VM Note that tests seem to be also VM dependent not only for tests order. Some tests expected results used Map which may be ordered differently on other VMs or other versions. This must also be fixed...
Entered bug 146215 for the order problem due to the different Map implementation.
Entered bug 146615 for the order problem in TypeHierarchyTests
Created attachment 44425 [details] Proposed patch ClasspathInitializerTests issue does no longer occur in HEAD stream => just force tests sort in maintenance stream
Released for 3.2.1 in TARGET_321 branch
Released for 3.3 M1 in HEAD (except change on ClasspathInitializerTests)
Verified for 3.3 M1 using build I20060804-0010.
Verified for 3.2.1 using build M20060908-1655 using JRockit VM.