Test Results

Logs 4.5.2

Performance Unit Test Results for 4.5.2

The table shows the unit test results for this build on the platforms tested. You may access the test results page specific to each component on a specific platform by clicking the cell link. Normally, the number of errors is indicated in the cell. A "-1" or "DNF" means the test "Did Not Finish" for unknown reasosns and hence no results page is available. In that case, more information can sometimes be found in the console logs.

Any unit test failures below have been investigated and found to be test-related and do not affect the quality of the build. See the sign-off page (bug 487552) for details.

org.eclipse
Component
Test Configurations
linux.gtk.x86_64_8.0 macosx.cocoa.x86_64_7.0 win32.win32.x86_7.0
ant.tests.*

ant.tests.ui

(0) (XML)--
compare.tests(0) (XML)--
core.tests.*

core.tests.resources

(0) (XML)--

core.tests.runtime

(4) (XML)--
jdt.core.tests.*

jdt.core.tests.performance

(0) (XML)--
jdt.debug.tests(0) (XML)--
jdt.text.tests(26) (XML)--
jdt.ui.tests.*

jdt.ui.tests.refactoring

(0) (XML)--

jdt.ui.tests

(0) (XML)--
pde.api.tools.tests(0) (XML)--
pde.ui.tests(0) (XML)--
swt.tests(0) (XML)--
team.tests.*

team.tests.cvs.core

(2) (XML)--
ua.tests(2) (XML)--
ui.tests.*

ui.tests.forms

(0) (XML)--

ui.tests.performance

(2) (XML)

NOTE: Remember that for performance unit test tables, there are never any "missing files" listed, if there are any. This is expected to be a temporary solution, until an exact fix can be implemented. For more details, see bug 451890.