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.

| JptCoreTests - random failure of spurious nature, will comment out if it continues to fail

−

JptUtilityTests - Package was not exported in manifest. Workspace tests did not reveal the problem. Need to run strict in workspace tests to identify this type of issue beforehand. Local build test run did catch the problem, but it was ignored and released anyway, assuming it was a local config problem. - njh

| The JPT Utility test has been fixed. The remaining JPT model test failure is a bit more interesting. Since this test has failed again (2 consecutive fails after 7 consecutive passes), it is possible that a recent change by us or in the facet or artifact edit frameworks is causing this failure. Unfortunately, we are unable to reproduce this failure locally using all of the latest code from WTP.

+

| Appears to be completely random--no changes in the component since 4/10. Even a sweep changing printStackTrace()s to failures resulted in nothing.

−

+

−

I have entered bug 221757 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=221757) to track the problem. We will comment out the test and insert some debug statement in hopes of discovering the cause of the failure. Since the problem doesn't occur locally, it should not affect the functionality of the plugin. - Neil

| 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.

| 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.

| 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

| 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.

Latest revision as of 22:43, 12 September 2008

Contents

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.