Jump to: navigation, search

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

< WTP‎ | Build
(M6 02/28)
 
(42 intermediate revisions by 9 users not shown)
Line 3: Line 3:
 
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.
 
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 03/06 ===
+
=== M7 04/17 ===
==== I20080306065043====
+
==== I20080424061315 ====
 
+
 
{| border="3"   
 
{| border="3"   
 
! width="10%" | Project  
 
! width="10%" | Project  
 
! width="30%" | Error Type Compile/JUnit/Respin  
 
! width="30%" | Error Type Compile/JUnit/Respin  
! Analysis/Initials  
+
! Analysis/Initials
  
 
|-
 
|-
! JPT
+
! Server tools
| 1 Junit failure in org.eclipse.jpt.core.tests.internal.JptCoreTests
+
| 1 JUnit compile failure in org.eclipse.jst.server.core.tests.impl.TestWebModule
1 Junit failure in org.eclipse.jpt.utility.tests.internal.JptUtilityTests
+
| Bug 213187 - Committer didn't have JUnit project checked out or run when making fix/TdB
|
+
|-  
+
! JEE
+
| 4 Junit failures in org.eclipse.jst.j2ee.tests.bvt.AutomatedBVT
+
|
+
 
|}
 
|}
  
=== M6 02/28 ===
 
==== I20080228113529 ====
 
  
 +
==== I20080417052146 ====
 
{| border="3"   
 
{| border="3"   
 
! width="10%" | Project  
 
! width="10%" | Project  
 
! width="30%" | Error Type Compile/JUnit/Respin  
 
! width="30%" | Error Type Compile/JUnit/Respin  
! Analysis/Initials  
+
! 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
 
| Changes to our line delimiter handling invalidated one of our tests.  It used to test if the default delimiter was the platform delimiter, but now the default is the one already in the document.  The document being tested was using the Windows line delimiter, so the test passed fine on Windows but would break on any other platform.  The test has been updated. /ND
 
|-
 
! 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.
 
|}
 
 
==== I20080228162856 ====
 
 
{| border="3" 
 
! width="10%" | Project
 
! width="30%" | Error Type Compile/JUnit/Respin
 
! Analysis/Initials
 
 
|-
 
|-
 
! JEE
 
! JEE
| 4 JUnit failures.
+
| 4 Junit failures in JEE org.eclipse.jst.j2ee.tests.bvt.AutomatedBVT
|testAddListener_Web24_Defaults - random failure - WebProject does not exist
+
| testDeleteModuleDependencyWithMarker - random failure - DependencyGraphManager does not report dependency between P/TestEAR and P/TestWeb <br>testRenameModuleDependencyWithMarker - random failure - DependencyGraphManager does not report dependency between P/TestEAR and P/newUtil /ccc
<p>testWebPublishJEE5 - random failure - Component TestUtil should have 2 component classpath dependencies, only has: 0
+
/ccc
+
 
|-
 
|-
! XML
+
! JSP
| 1 Junit failure in org.eclipse.wst.xml.core.tests.SSEModelXMLTestSuite
+
| 1 Junit failure in org.eclipse.jst.jsp.core.tests.JSPCoreTestSuite
| Above update missed the build./ND
+
| Appears to be completely random--no changes in the component since 4/10.  Even a sweep changing printStackTrace()s to failures resulted in nothing.
 
|-
 
|-
! Releng
+
! JSF PageDesigner
| 1 Junit failure in org.eclipse.wtp.releng.tests.TestBuild
+
| 1 Junit failure in org.eclipse.jst.pagedesigner.tests.AllTests
| Same Versioning Errors (in JSF, Common Facet). JSF can not easily update, since other changes have been made to HEAD.
+
| The failing test in the pagedesigner area appears to be one of those intermittent, random problems
 
|}
 
|}
 
==== I20080228214133 ====
 
 
{| border="3" 
 
! width="10%" | Project
 
! width="30%" | Error Type Compile/JUnit/Respin
 
! Analysis/Initials
 
|-
 
! JEE
 
| 2 JUnit failures.
 
|testClassFolderDependency - random failure - Component TestWeb should have 1 component classpath dependencies, only has: 0/ccc
 
|-
 
! JPT
 
| Massive compile failure. Seems a number of source files are missing?
 
| Releasing process failure.  Sync error displayed at end of release process, manual inspection looked OK but there were apparently problems (files left untagged that had moved).  Not sure what went wrong with the process (standard releng tool was used, perhaps a CVS glitch?).  Manually tagging and re-releasing changed plugins to fix the problem /njh
 
 
I also want to note this release was done only to update JavaDoc. The JPT team felt this was critical to do this week, but normally, JavaDoc changes should not be released after candidate produced, since normally that would not be a blocking or critical  problem ... so, remember ... every release is an opportunity to break something. dw
 
|-
 
! Releng
 
| 1 Junit failure in org.eclipse.wtp.releng.tests.TestBuild
 
| Same Versioning Errors (in JSF, Common Facet). JSF can not easily update, since other changes have been made to HEAD.
 
|}
 
 
==== I20080229031047 ====
 
 
{| border="3"
 
! width="10%" | Project
 
! width="30%" | Error Type Compile/JUnit/Respin
 
! Analysis/Initials
 
|-
 
! JPT
 
| Same massive compile failure as previous build. Assuming fix isn't in yet
 
| Releasing process failure.  Sync error displayed at end of release process, manual inspection looked OK but there were apparently problems (files left untagged that had moved).  Not sure what went wrong with the process (standard releng tool was used, perhaps a CVS glitch?).  Manually tagging and re-releasing changed plugins to fix the problem /njh
 
|}
 
 
==== I20080229065303 ====
 
 
{| border="3"
 
! width="10%" | Project
 
! width="30%" | Error Type Compile/JUnit/Respin
 
! Analysis/Initials
 
|-
 
! WS
 
| Respin requested based on bad bug (regression) found in smoke test.
 
|The Web Services smoke test failed due to a change in the Tomcat server tools [https://bugs.eclipse.org/bugs/show_bug.cgi?id=220879 220879].  The problem was fixed by Server tooling team and was dropped in I20080229195548.  Based on the comments in the bug, this was due to a change in publishing in Tomcat server tools recently and was not found because testing was not done in a new workspace.  They had commented that new JUnit would be included in the next I-build to catch this in the future. (KSC)
 
|}
 
 
==== I20080229121121 ====
 
 
{| border="3"
 
! width="10%" | Project
 
! width="30%" | Error Type Compile/JUnit/Respin
 
! Analysis/Initials
 
|-
 
! releng
 
| WS fix not in yet. Unclear what kicked off this build. No change in map files from previous. Either someone did "manually", or, bug in CruiseControl.
 
| action: will keep an eye on this, and if continues to happen will experiment with CC settings, or upgrate to 2.7.2 EA, or disable manual force build. (If others committers do 'manually', for any reason, that's fine ... just let Helen or David know). dw
 
|}
 
 
==== I20080229195548 ====
 
 
{| border="3"
 
! width="10%" | Project
 
! width="30%" | Error Type Compile/JUnit/Respin
 
! Analysis/Initials
 
|-
 
! JSF
 
| JUnit breakage due to core exception while deleting project tearDown.
 
| The failure in I20080229195548 is new and indeed spurious.  It stems from the standard class of problem we have identified where project contents are being file locked in ways that previously they either weren't or in ways that are more susceptible to race conditions.  Once we get past code review I will endeavour to convert to the busy loop idiom for deleting projects across all of our JUnit tests.  CB.
 
|}
 
 
==== I20080301004930 ====
 
 
{| border="3"
 
! width="10%" | Project
 
! width="30%" | Error Type Compile/JUnit/Respin
 
! Analysis/Initials
 
|-
 
! SSE (JSP)
 
| Another, apparently 'random' error in JSP JUnits, no change in map files from previous build.
 
|
 
|}
 
 
 
 
 
  
  
 +
* Other milestones
 +
:[http://wiki.eclipse.org/WTP_Build_Break_Board_M6 Build Breaker Board M6]
  
  
[[Category:Eclipse Web Tools Platform Project]]
+
[[Category:WTP Build Related| ]]

Latest revision as of 23:43, 12 September 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.

M7 04/17

I20080424061315

Project Error Type Compile/JUnit/Respin Analysis/Initials
Server tools 1 JUnit compile failure in org.eclipse.jst.server.core.tests.impl.TestWebModule Bug 213187 - Committer didn't have JUnit project checked out or run when making fix/TdB


I20080417052146

Project Error Type Compile/JUnit/Respin Analysis/Initials
JEE 4 Junit failures in JEE org.eclipse.jst.j2ee.tests.bvt.AutomatedBVT testDeleteModuleDependencyWithMarker - random failure - DependencyGraphManager does not report dependency between P/TestEAR and P/TestWeb
testRenameModuleDependencyWithMarker - random failure - DependencyGraphManager does not report dependency between P/TestEAR and P/newUtil /ccc
JSP 1 Junit failure in org.eclipse.jst.jsp.core.tests.JSPCoreTestSuite Appears to be completely random--no changes in the component since 4/10. Even a sweep changing printStackTrace()s to failures resulted in nothing.
JSF PageDesigner 1 Junit failure in org.eclipse.jst.pagedesigner.tests.AllTests The failing test in the pagedesigner area appears to be one of those intermittent, random problems


  • Other milestones
Build Breaker Board M6