RE: [wtp-releng] Was release/respin intentional? and current status....

[David M Williams <david_williams@xxxxxxxxxx>]

> Should I change the status
to "green" in this case? This status change won't make the release
better :-)

I'd say yes. Let's reserve the red-x to mean
"Stop! don't declare this build!". 
And ... just list bad bugs we think should
be part of the announcement. 
And ... remember, we could ask for a platform
respin if we really thought it blocking! 
But, I didn't get that impression from my
quick reading of 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=207580

And ... I appreciate you trying to get the
performance test and scan's running again ... so don't 
wear the clown nose for long. :)

"Raev, Kaloyan" <kaloyan.raev@xxxxxxx>
Sent by: wtp-releng-bounces@xxxxxxxxxxx

11/14/2007 06:41 PM

Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>

To	"Webtools releng discussion list" <wtp-releng@xxxxxxxxxxx>
cc
Subject	RE: [wtp-releng] Was release/respin intentional? and current        status....

About the red X on JEE team. 
Yes, it would normally means "Stop!
Don't declare this build" until we fix this severe bug 207580. 
But since it is a Platform bug
and Platform M3 is already closed, we have no choice, except to live with
it and declare M3 with this bug. 
It is a good idea to have this
announcement note with serious bugs.
 
Should I change the status to
"green" in this case? This status change won't make the release
better :-)
 
Greetings,
Kaloyan

---

From: wtp-releng-bounces@xxxxxxxxxxx
[mailto:wtp-releng-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Wednesday, November 14, 2007 6:36 PM
To: neil.hauge@xxxxxxxxxx; Webtools releng discussion list
Subject: Re: [wtp-releng] Was release/respin intentional? and current
status.... 


Thanks Neil. Since the test intermittently fails (thereby intermittently
giving the impression the build is bad) it'd be best to change the test
so that runs, prints diagnostics to the log, where you can read them over
time, but not to actually cause a "fail" ... at least until you
think it's fixed, that is. 

But ... it didn't fail in the last build, so we'll go with that one for
our M3. 
http://download.eclipse.org/webtools/committers/drops/R3.0/S-3.0M3-20071114072506/


There's still some issue with the test results page at: 
http://wiki.eclipse.org/WTP_Functional_Test_R30_M3

Three teams haven't reported yet! 
But, I'll assume all is ok, since it's a bit late for a respin.  
Please update the table when you're done testing. 
Also, I noticed the JEE team put a red X there. Normally a red X means
"Stop! don't declare this build" ... but, reading the bugs, I
don't think that's what's intended. 
Please correct me if I'm wrong. 

Helen will include all "serious bugs" found on the announcement
note, as well as note teams who didn't report status, to warn potential
users and adopters. 

Thanks,

Neil Hauge <neil.hauge@xxxxxxxxxx>
Sent by: wtp-releng-bounces@xxxxxxxxxxx

11/14/2007 09:54 AM

Please respond to
neil.hauge@xxxxxxxxxx; Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>

To	Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
cc
Subject	Re: [wtp-releng] Was release/respin intentional?

The JPT test failure as you suspect is something that only fails occasionally
in the build.  We have been looking at this for several days but have
been unable to determine what is causing the failure.  Part of the
problem is that we have been unable to observe this test failure while
running the tests locally.  It only happens sometimes during the build
tests, making it very difficult to debug.

We haven't been able to reproduce this behavior while using Dali either,
but the test does indicate a real potential problem.  So, I think
the test is valid, and for some reason manages to fail occasionally in
the build.  Honestly, by looking at the code, we're not quite sure
how it could be failing at all.  

Thanks for opening the bug.  We will update it later this morning
with any new information we have.

Neil

David M Williams wrote: 

sse.doc.user and the new service.policy seemed to have been re-released
... a respin occurred ... and a JPT JUnit test failed?! 

Were these releases intentional for M3? Can the JPT team see if the JUnit
test is serious? 

Thanks, 




938c938 
< plugin@xxxxxxxxxxxxxxxxxxxxxxxxxxxx=v200705302225,:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/webtools,,wst/components/doc/plugins/org.eclipse.wst.sse.doc.user
--- 
> plugin@xxxxxxxxxxxxxxxxxxxxxxxxxxxx=v200711131723,:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/webtools,,wst/components/doc/plugins/org.eclipse.wst.sse.doc.user
1116c1116 
< plugin@xxxxxxxxxxxxxxxxxx.service.policy=v200711122056,:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/webtools,,wst/components/ws/plugins/org.eclipse.wst.ws.service.policy
--- 
> plugin@xxxxxxxxxxxxxxxxxx.service.policy=v200711132021,:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/webtools,,wst/components/ws/plugins/org.eclipse.wst.ws.service.policy
1144c1144 
< plugin@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=v200711122056,:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/webtools,,wst/components/ws/plugins/org.eclipse.wst.ws.service.policy.ui
--- 
> plugin@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=v200711131703,:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/webtools,,wst/components/ws/plugins/org.eclipse.wst.ws.service.policy.ui

---

_______________________________________________
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

Attachment: smime.p7s
Description: Binary data