Re: [wtp-releng] Smoke Test Request for WTP 3.2 I-build towards WTP 3.2

[David M Williams <david_williams@xxxxxxxxxx>]

Thanks for the quick investigation Nick. 

As a matter of process, it is best to open a bug just to track the fix to 
the test so if/when others see the JUnit failure, we'd have something to 
point them to for more detail.




From:
NICHOLAS SANDONATO/Durham/IBM@IBMUS
To:
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
Date:
10/15/2009 11:22 AM
Subject:
Re: [wtp-releng] Smoke Test Request for WTP 3.2 I-build towards WTP 3.2 M3
Sent by:
wtp-releng-bounces@xxxxxxxxxxx




It's a problem with the test.  The expected output will need to be 
changed. 


From: 
NICHOLAS SANDONATO/Durham/IBM@IBMUS 
To: 
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx> 
Date: 
10/15/2009 11:07 AM 
Subject: 
Re: [wtp-releng] Smoke Test Request for WTP 3.2 I-build towards WTP 3.2   
M3 
Sent by: 
wtp-releng-bounces@xxxxxxxxxxx





I'm investigating the HTML failure.  It shouldn't affect others' smoke 
testing. 

From: 
David M Williams/Raleigh/IBM@IBMUS 
To: 
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx> 
Date: 
10/15/2009 10:59 AM 
Subject: 
[wtp-releng] Smoke Test Request for WTP 3.2 I-build towards WTP 3.2 M3 
Sent by: 
wtp-releng-bounces@xxxxxxxxxxx





Smoke Test Request for WTP 3.2 I-build towards WTP 3.2 M3

Please document your Project's testing and approval of build, by today, 
Thursday, 2 PM (Eastern Time), or let us know if that's not possible.

There is one HTML Parser JUnit failure that should be addressed. 

The JAXWS functionality appears for the first time in this week's I-build. 


Please note the new 'emf validation' pre-req for that functionality. 
While the JAXWS team will smoke test the JAXWS specific function, others 
should 
sanity check that there's no "interference" from the new function. That 
is, 
all the "old" webservices stuff works as expected. (There is no reason
to think it wouldn't work fine ... I'm just saying to sanity check and 
keep an eye open). 
This JAXWS function is technically still in incubation, but is expected to 

graduate 
soon, in a couple of milestones. 

Current Build
http://build.eclipse.org/webtools/committers/wtp-R3.2.0-I/20091015040800/I-3.2.0-20091015040800/


Smoketest Results
http://wiki.eclipse.org/WTP_Smoke_Test_Results_R32_101509


BTW, I'm not sure why the build took 11 hours! I'm guessing it was just an 

infrastructure overload issue and 
we were "swapped out" for many hours. There were no such issues on similar 

warm-up builds so I do not think it will be an ongoing issue. 


_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng

_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng

_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng