| Re: [wtp-releng] Junit failure on I20080229195548 and I20080301004930 |
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.
There was no JSF-caused breakage in I20080301004930. I think you are confusing us with JSP Core.
--Cam
--- Original Message ---
I suggest we go ahead and declare I20080301004930. There was another, different JUnit failure in JSF code, but would assume it's another of those "random" ones. (there was no change in map files from previous build). I'll also add the "final" four builds from this week's sequence to our "Build Break Board" that Webservices and JSF teams will need to update. I20080229065303 - WS requested respin based on bug found in smoke test. I20080229121121 - unclear what kicked off this build. no change in map files from previous. Either someone did "manually", or, bug in CruiseControl. I20080229195548 - WS bug fixed, but apparently 'random' error in JSF I20080301004930 - another, different 'random' error in JSF, no change in map files from previous build. The fact that it took us 8 builds to get one to declare (7 after the one that was supposed to be the weekly I-build) and even then that build contained JUnit errors is a good indication that this build break board should quickly provide some useful amount of data :) WS and JSF teams, no need to dwell over it, but please update with a quick explanation of what happened and what could maybe be done differently in future. Thanks,
Hi, This last build I-I20080229195548-20080229195548 has a JUnit failure with org.eclipse.jst.jsf.facesconfig.ui.test.AllTestCases Was there anything else that was dropped that could've caused this? Can this build be declared as this week's I build with this issue? Regards, Helen Zhang
Hi, We have verified that the problem reported in bug 220879 has been fixed and Web services tools smoke test has passed with the WTP 3.0 I-I20080229195548-20080229195548 driver. Regards, Kathy Chan Rational Java Web Services, IBM Toronto Lab kathy@xxxxxxxxxx (905) 413-3022, tieline: 313-3022 ----- Forwarded by Kathy Chan/Toronto/IBM on 02/29/2008 07:34 PM -----
Hi, Just to keep everyone posted on the failing Web services smoke test for this week's I-build. We found 2 problems with this week's driver: https://bugs.eclipse.org/bugs/show_bug.cgi?id=220879 https://bugs.eclipse.org/bugs/show_bug.cgi?id=220877 Server tooling has dropped the fix for 220879 and we are waiting for a good build to re-run smoke test on (the current build I20080229182755 that's running should contain the fix). As for bug 220877, it's a problem with build.properties. We will drop the fix once this week's I-build is declared. This only affect Web services Ant scenario in the IDE. Users affected by this problem could go to the bugzilla attachment to pick up a patched JAR that contain this fix. Regards, Kathy Chan Rational Java Web Services, IBM Toronto Lab kathy@xxxxxxxxxx (905) 413-3022, tieline: 313-3022 ----- Forwarded by Kathy Chan/Toronto/IBM on 02/29/2008 03:49 PM -----
Please smoketest the below WTP 3.0 weekly I build and update the smoketest page with your results. Thank you! Build http://build.eclipse.org/webtools/committers/wtp-R3.0-I/20080228162856/I-I20080228162856-20080228162856/ Smoketest Results http://wiki.eclipse.org/WTP_Smoke_Test_Results_R30_022808 Note: There are 6 Junit failures, XML ones are already fixed, and the J2EE ones appears to be random. Regards, Helen Zhang |