Skip to main content
Jump to: navigation, search

Difference between revisions of "WTP/Build/WTP Build Break Board"

< WTP‎ | Build
(WTP weekly I build breakages)
(M6 02/28 Build I-I20080228113529-20080228113529)
Line 27: Line 27:
 
! Releng
 
! Releng
 
| 1 Junit failure in org.eclipse.wtp.releng.tests.TestBuild
 
| 1 Junit failure in org.eclipse.wtp.releng.tests.TestBuild
|  
+
| Versioning Errors. Plugin versions went '''down''' compared to 202 release. Appeared this week since reference data was just updated, but the error has probably existed for a while. One contributing factor was perhaps that the "build failed" notifications were broken for several days (not being sent) so may have not been noticed by development teams.
 
|}
 
|}

Revision as of 18:45, 28 February 2008

WTP weekly I build breakages

The purpose of this board is to track the list of breakages that we have on our weekly I builds. Compile, JUnit, respin requests that cause a delay in smoketest and thus declaration of our builds. We hope to find a pattern with these breakages so that we can learn from them and the same mistakes can be avoided in future.


M6 02/28 Build I-I20080228113529-20080228113529

Project Error Type Compile/JUnit/Respin Analysis/Initials
Server 3 compile errors in org.eclipse.jst.server.ui.tests Didn't run local junit test after removing a class. / AV
JPT DNF in Junit for org.eclipse.jpt.core.tests.internal.JptCoreTests Deadlock in the tests, deleting resources. Seems to be a test issue, still investigating root cause / njh
Server 2 Junit failures in org.eclipse.jst.server.ui.tests.AllTests Related to the compilation errors / AV
XML 1 Junit failure in org.eclipse.wst.xml.core.tests.SSEModelXMLTestSuite
Releng 1 Junit failure in org.eclipse.wtp.releng.tests.TestBuild Versioning Errors. Plugin versions went down compared to 202 release. Appeared this week since reference data was just updated, but the error has probably existed for a while. One contributing factor was perhaps that the "build failed" notifications were broken for several days (not being sent) so may have not been noticed by development teams.

Back to the top