I released changes to fix the version issue in the test bundle,
but why are these checks even covering test bundles?
- Konstantin
From:
wtp-releng-bounces@xxxxxxxxxxx [mailto:wtp-releng-bounces@xxxxxxxxxxx] On
Behalf Of David M Williams
Sent: Thursday, January 28, 2010 5:49 AM
To: wtp-releng@xxxxxxxxxxx
Subject: [wtp-releng] Smoke Test Request for WTP 3.2.0 S-build
Smoke Test Request for WTP
3.2.0 S-build
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.
I am a torn about making
this request. Teams may want to wait until the next build, but it won't be
ready until after noon, and we will probably need another build after that!
There are several issues:
There is another S-build
already running this morning (started an hour ago, or so, which means someone
checked in a change after the deadline ... or at least near midnight? and I do
not know what change was checked in that kicked off that build).
There are a number of Unit
tests failures, spanning lots of function: xml, jsp, jsf, jpa -- so lots of investigation
and presumably some fixes need to be done.
In the last build, there's
still one more "versioning error" that would require a fix and respin
to have a green build.
Bundles with qualifier-only increases
org.eclipse.wst.common.project.facet.core.tests
1.4.0.v201001141844 (current)
1.4.0.v200902182122 (reference)
So, I'll leave it up to
each team. You may smoke test now, with the caveat that you may decide to also
smoke test the next build(s),
depending on what fixes are
needed to clean up?
Please report to wtp-releng
as teams investigate, and make plans to produce a suitable milestone build.
Current Build
http://build.eclipse.org/webtools/committers/wtp-R3.2.0-S/20100128031257/S-3.2.0M5-20100128031257/
Smoketest Results
http://wiki.eclipse.org/WTP_Smoke_Test_Results_R320_01282010
