Community
Participate
Working Groups
SeparateVMTests.testBuild and testBuildMinusDebug have been failing. Need to make them pass or explain the failures.
changes made to the ant test suite during 3.1 improved the reliability of the tests, but made them run slower in some cases. See bug #82598. Specifically, in the 3.0 test suite, a launched build file does not always wait for the console to complete before proceding, in the 3.1 test suite the test always wait for the console closed notification. This may account for some of 3.1 test failures (or at least contribute to those failures)
I was wrong. The measured runs do wait for the console closed notification, it's only the first unmeasured launch that does not. Still investigating.
launching is slower in 3.1 than it was in 3.0. This is at least partially due to the console. It takes longer to create a console than it used to. Have to test enablement expressions for pattern matchers, create pattern matchers from extension, and compile the patterns. None this had to be done in 3.0. (not giving up on making this faster yet)
Created attachment 22844 [details] performance test using regular java class Launches a HelloWorld type application. Demonstrates 3.1 launching is slower in general.
We have investigated the performance, made some tweaks. Time to move on :-)
