<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
It was failing for me when I updated the issue and I am using the WS
3.0.2.GA release, so I'm confused by that. I'll try updating both the
tck and jbossas workspaces to see what my current status is.<br>
<br>
Heiko Braun wrote:
<blockquote cite="mid:1214238853.9966.2.camel@localhost.localdomain"
type="cite">
<pre wrap="">
You don't need to. The test passes for locally.
I did resolve that issue, but still try to figure out why is passes.
Maybe it's related to the WS update to 3.0.2.
/Heiko
On Mon, 2008-06-23 at 08:59 -0700, Scott Stark wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Any direction on this? I want to get past this issue today without
having to spend too much time digging into the details of the tck test
harness.
-------- Original Message --------
Subject:
Re: TCK5 status (06/20)
Date:
Sun, 22 Jun 2008 18:49:04 -0700
From:
Scott Stark <a class="moz-txt-link-rfc2396E" href="mailto:sstark@redhat.com"><sstark@redhat.com></a>
To:
Rajesh Rajasekaran
<a class="moz-txt-link-rfc2396E" href="mailto:rrajasek@redhat.com"><rrajasek@redhat.com></a>
CC:
JavaEE-TCK <a class="moz-txt-link-rfc2396E" href="mailto:javaeetck@jboss.org"><javaeetck@jboss.org></a>
References:
<a class="moz-txt-link-rfc2396E" href="mailto:1213949201.3626.4.camel@nymph.grauwnet.nerdnet.nl"><1213949201.3626.4.camel@nymph.grauwnet.nerdnet.nl></a> <a class="moz-txt-link-rfc2396E" href="mailto:485B6D93.20505@redhat.com"><485B6D93.20505@redhat.com></a> <a class="moz-txt-link-rfc2396E" href="mailto:1213951820.10747.10.camel@localhost.localdomain"><1213951820.10747.10.camel@localhost.localdomain></a> <a class="moz-txt-link-rfc2396E" href="mailto:485B71E4.9080209@redhat.com"><485B71E4.9080209@redhat.com></a> <a class="moz-txt-link-rfc2396E" href="mailto:485BBF63.8010009@redhat.com"><485BBF63.8010009@redhat.com></a>
I have assigned JBCTS-814 back to Heiko as I don't see how the
getSharedObject() value the client is using to obtain the service
relates to anything we are setting up in the client. This test does not
use injection, and the client env has a binding for the service, so let
me know how this is supposed to propagate to the test service field.
Rajesh Rajasekaran wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Overall: 93.95%
4.38% increase from last week
Modules at 100%
interop-integration, interop-naming, interop-rmiiiop,
interop-security, interop-tx, interop-csiv2, saaj
ejb3-core - (74% - back to and better than Beta4 results)
However down from the 78% yesterday (Blocker), due to changes put in
for JBCTS-540, Carlo investigating, follow up on separate thread.
ejb3-persistence - At 99%, up 7% from last week - outstanding issues
on spreadsheet
Blockers:
(Affecting webservices, webservices12, jws, jaxws, jaxrpc,
interop-webservices)
<a class="moz-txt-link-freetext" href="http://jira.jboss.com/jira/browse/JBCTS-814">http://jira.jboss.com/jira/browse/JBCTS-814</a>
<a class="moz-txt-link-freetext" href="http://jira.jboss.com/jira/browse/JBCTS-813">http://jira.jboss.com/jira/browse/JBCTS-813</a>
The spreadsheet has been updated to reflect the latest outstanding
JIRA's.
Modules certified: 24
Modules remaining : 13
Detailed results:
<a class="moz-txt-link-freetext" href="https://svn.corp.jboss.com/repos/tck/reports/weekly/TCK5-JBossAS5.0.0.GA.xls">https://svn.corp.jboss.com/repos/tck/reports/weekly/TCK5-JBossAS5.0.0.GA.xls</a>
<a class="moz-txt-link-freetext" href="http://intranet.corp.redhat.com/ic/intranet/CTS50TestResults.html">http://intranet.corp.redhat.com/ic/intranet/CTS50TestResults.html</a>
Adding comments from Dimitris which summarizes the status.
Dimitris Andreadis wrote:
</pre>
<blockquote type="cite">
<pre wrap="">The best TCK results we've got with Beta4 had:
assembly - 7 failures
ejb - 4 failures
ejb30+persistence - 313 failures
jacc - 2 failures
servlet - 2 failures
signature - 4 failures
--------------
332
So we need to get rid of:
appclient - 3 failures
jaxrpc - 245 failures
jaxws - 709 failures
(servlet) - 10 failures
webservices - 156 failures
jws - 101 failures
webservices12 - 61 failures
interop-webservices - 67 failures
----------------
1352 failures
Or more or less all the webservice (+appclient +couple of servlet
ones) regression.
My read
of the last 2 TCK runs is that:
We got significant (+3.5%) improvement from:
- Ales' VFS fix
- Stefan's stubs resolution
- Rejesh descriptor fixes
- JBossXB update
- ... other changes I forget
We got sidetracked (-0.5%) by
- the JBCTS-540 (+metadata org.jboss.metadata.jbmeta11) hack, that
probably conflicts with Scott's "change the LegacyEjb3JndiPolicy ejb3
REMOTE_HOME to ejbName/home from baseJndiName+"Home"
And the upgrade to ejb3-core 0.1.5 was not performed as yet.
The current pass rate for tck is 93.95%
Since most of the other release criteria are met (Seam is running, AS
testsuite in good shape, AS JIRA almost there) I think the EJB3 team
together with Scott should focus on the JNDI issue resolved *ASAP*.
Ales is looking at the other VFS issue + profileservice, while
everyone else keeps closing JBAS/JBCTS tasks or continues with AS
testsuite improvements.
If you manage to tackle the JNDI issue and we get a good TCK run, we
should be able to release early next week.
</pre>
</blockquote>
</blockquote>
<pre wrap="">_______________________________________________
jbossws-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbossws-dev@lists.jboss.org">jbossws-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbossws-dev">https://lists.jboss.org/mailman/listinfo/jbossws-dev</a>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>