With respect to the org.eclipse.jst.ws.tests, I have
recently found a thread safety issue with respect to ModuleStructuralModel via
its dependence on org.eclipse.emf.ecore.resource.impl.ResourceSetImpl, which in
turn depends on org.eclipse.emf.common.util.BasicEList. I believe the
exception that appears in the failure fits one of the scenarios that can occur
with concurrent access to ModuleStructuralModel. If so, this would be a
hit or miss occurrence.
I started filling a bug report, but got stuck trying to
come up with a reproducible test case to demonstrate the problem that doesn't
involve our SAS plug-ins. I'll go ahead file report today with
explanations and hopefully add a test case to demonstrate it in a
development environment later.
Cheers,
Larry
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Lanuti
Sent: Friday, November 10, 2006 12:18 PM
To: [email protected]
Subject: [wtp-dev] Still waiting on smoke test results for WTP 2.0 andfailing Junits?
Hey guys, (sorry for hitting the general list, but I know a lot of component leads are out and people may not be following the releng list)
So far, only server, SSE, WSDL, and XSD have reported any smoke test results for WTP 2.0. As a reminder, this is something that MUST be done before noon on Friday's so we can predictably deliver integration drivers. What's going on with the rest of the teams?
Also, we have 2 failing JUnits from web services and SSE. Care to comment? Should we not declare an integration build this week?
org.eclipse.jst.jsp.core.tests_
org.eclipse.jst.ws.tests_
Thanks,
John Lanuti
IBM Web Tools Platform Technical Lead, IBM Rational
IBM Software Lab - Research Triangle Park, NC
[EMAIL PROTECTED]
t/l 441-7861
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
