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.

I20080320151231

I20080320095049

Project

Error Type Compile/JUnit/Respin

Analysis/Initials

JSF

Respin requested for this build to address regression defect 223399. This change should not affect any other team.

GK - As part of the JSF facet installation, we add servlet and mapping entries to the web model. We were apparently using the model provider API's incorrectly, and when a change was made in javaee code, we broke.

JEE

4 Junit failures in JEE org.eclipse.jst.j2ee.tests.bvt.AutomatedBVT

Carl A -I just recommented out the two test cases that have been repeatedly failing in the recent I builds - bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=222626 is tracking this problem. (Unfortunately, we have been unable to recreate the failures locally, but we will continue to investigate.) These failures should not hold up the smoke test, and this change has been released for a build.

M6 03/13

I20080317220921

Project

Error Type Compile/JUnit/Respin

Analysis/Initials

JEE

Respin for this build as needed to address regression defect 222681/222321

ccc - Chuck put in code for bug 222321 that released the EMF models associated with a resource when the resource was written or deleted. Unfortunately, it released all of the Java EMF models when a jar was written or deleted (there were checks for .class and .java, but not .jar) It caused bug 222681.

Java EE

2 Junit failures in org.eclipse.jst.j2ee.tests.bvt.AutomatedBVT

ccc - this is another random failure- see bug 221798

I20080314073909

Project

Error Type Compile/JUnit/Respin

Analysis/Initials

JEM

28 Junit failure in org.eclipse.jem.tests.AllSuites

ccc - 28 of these errors appear to be specific to the build machine. Opened 222630 to address the other 2 errors - should not block smoke test

Java EE

2 Junit failures in org.eclipse.jst.j2ee.tests.bvt.AutomatedBVT

ccc - random failure, should not block smoke test

I20080314031658

Project

Error Type Compile/JUnit/Respin

Analysis/Initials

JSF

73 compile errors in org.eclipse.jst.jsf.metadata.tests

116 compile errors in org.eclipse.jst.pagedesigner.tests

JEM

28 Junit failure in org.eclipse.jem.tests.AllSuites

ccc - 28 of these errors appear to be specific to the build machine. Opened 222630 to address the other 2 errors - should not block smoke test

JSF

293 Junit failures probably due to compile errors in the jsf test suites

I20080306065043

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

I20080306160447

Project

Error Type Compile/JUnit/Respin

Analysis/Initials

JPT

1 Junit failure in org.eclipse.jpt.core.tests.internal.JptCoreTests

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.

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

JEE

46 Junit failures in org.eclipse.jst.j2ee.tests.bvt.AutomatedBVT

I20080306230652

Project

Error Type Compile/JUnit/Respin

Analysis/Initials

JEE

2 Junit failures in org.eclipse.jst.j2ee.tests.bvt.AutomatedBVT

testAddFilter_Web25_Defaults failed again in latest build I20080306230652.
I have found a related exception logged in the SysErrorLog of the test logs.
I have open https://bugs.eclipse.org/221798 to track the issue. Kaloyan

M6 02/28

I20080228113529

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

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.

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

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

Project

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

Project

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

Project

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.