Running all the OASIS Assembly tests this morning i'm getting just 9
tests failing so thats over 90% passing.
(To get these numbers requires all the local fixes mentioned in the
various JIRAs about issues in the OASIS tests, and yes that doesn't
include the false positives where a test is passing
I think I might take a look to see if I can make any sense of the
policy matching one. Bit tricky as I know the policy stuff hasn't been
brought up fully yet but at least it will be an education as to what
has been done so far.
Simon
Congratulations! I will be going over your progress this weekend to submit
the final GSoC evaluation before the Monday deadline. We can chat again if
you would like to have a discussion about your project before the final
eval.
On Thu, Aug 20, 2009 at 4:29 PM, lookman sanni lookous...@gmail.com
Folks,
I am *extremely* grateful for all the good work that is going on around the
testcases.
You are all helping both get Tuscany in shape and ALSO helping get the
testcases into shape.
It is with the latter that I'd like to ask for your help.
I realize that there are problems in some of
[
https://issues.apache.org/jira/browse/TUSCANY-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3222:
---
Component/s: (was: Java SCA Core Runtime)
OASIS Compliance
Clarrify with
Hi Mike
Happy to do that. To date if you look for Tuscany JIRA with titles
starting with the word (OASIS) then these usually refer to an OASIS
fix being required. Not a general rule I admit. Also look here
(http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Conformance+Testing)
for a summary
On Fri, Aug 21, 2009 at 2:04 PM, Mike
Edwardsmike.edwards.inglen...@gmail.com wrote:
Folks,
I am *extremely* grateful for all the good work that is going on around the
testcases.
You are all helping both get Tuscany in shape and ALSO helping get the
testcases into shape.
It is with the
How about also a new JIRA component for this, i've just added one
OASIS Compliance and will start moving existing jiras there -
https://issues.apache.org/jira/browse/TUSCANY/component/12313003
...ant
+1 that adds an extra dimension too.
Simon
On Fri, Aug 21, 2009 at 2:12 PM, Simon Lawssimonsl...@googlemail.com wrote:
How about also a new JIRA component for this, i've just added one
OASIS Compliance and will start moving existing jiras there -
https://issues.apache.org/jira/browse/TUSCANY/component/12313003
...ant
+1 that adds
Although perhaps we need more than that, for example i was about to
move TUSCANY-3231 there but its a Tuscany issue not an OASIS test
issue, do we need a component specifically for things in the OASIS
code?
...ant
I thought that was what you mean in the first instance.
Simon
[
https://issues.apache.org/jira/browse/TUSCANY-3206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3206:
---
Component/s: (was: Java SCA Verification Tests)
OASIS Compliance
OASIS fixes
[
https://issues.apache.org/jira/browse/TUSCANY-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3190:
---
Component/s: OASIS Compliance
OASIS fixes required to make ASM_8004 and ASM_12005/7/8/9/10/11 and
[
https://issues.apache.org/jira/browse/TUSCANY-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3219:
---
Component/s: (was: Java SCA Assembly Model)
OASIS Compliance
SCA 2.x otest
[
https://issues.apache.org/jira/browse/TUSCANY-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3223:
---
Component/s: (was: Java SCA Core Runtime)
OASIS Compliance
Mutual exclusive
[
https://issues.apache.org/jira/browse/TUSCANY-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3189:
---
Component/s: OASIS Compliance
OASIS fixes required to make ASM_8003 work
[
https://issues.apache.org/jira/browse/TUSCANY-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3225:
---
Component/s: (was: Java SCA Assembly Model)
OASIS Compliance
[
https://issues.apache.org/jira/browse/TUSCANY-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3224:
---
Component/s: (was: Java SCA Assembly Model)
OASIS Compliance
TestCase is not
[
https://issues.apache.org/jira/browse/TUSCANY-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3229:
---
Component/s: (was: Java SCA Assembly Model)
OASIS Compliance
[
https://issues.apache.org/jira/browse/TUSCANY-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3205:
---
Component/s: OASIS Compliance
OASIS otest ASM_5033_TestCase has invalid composte
[
https://issues.apache.org/jira/browse/TUSCANY-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3228:
---
Component/s: (was: Java SCA Assembly Model)
OASIS Compliance
[
https://issues.apache.org/jira/browse/TUSCANY-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3191:
---
Component/s: OASIS Compliance
OASIS fixes required to make ASM_8010 work
[
https://issues.apache.org/jira/browse/TUSCANY-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3221:
---
Component/s: (was: Java SCA Core Runtime)
OASIS Compliance
Intents attached
[
https://issues.apache.org/jira/browse/TUSCANY-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3226:
---
Component/s: (was: Java SCA Assembly Model)
OASIS Compliance
[
https://issues.apache.org/jira/browse/TUSCANY-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3220:
---
Component/s: (was: Java SCA Core Runtime)
OASIS Compliance
OASIS
[
https://issues.apache.org/jira/browse/TUSCANY-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3194:
---
Component/s: OASIS Compliance
OASIS fixes required to make ASM_9003 work
[
https://issues.apache.org/jira/browse/TUSCANY-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3197:
---
Component/s: OASIS Compliance
OASIS otest fixes - rename BaseJAXWSTestCase.java to not end with
[
https://issues.apache.org/jira/browse/TUSCANY-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3227:
---
Component/s: (was: Java SCA Assembly Model)
OASIS Compliance
[
https://issues.apache.org/jira/browse/TUSCANY-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3230:
---
Component/s: OASIS Compliance
OASIS otest ASM_6009_TestCase missing space in config.output string
[
https://issues.apache.org/jira/browse/TUSCANY-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3218:
---
Component/s: OASIS Compliance
OASIS otest ASM_5016_TestCase uses Service1 not Service1Superset
[
https://issues.apache.org/jira/browse/TUSCANY-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3214:
---
Component/s: OASIS Compliance
OASIS fixes required to make ASM_5015 and ASM_6017 work - blank
[
https://issues.apache.org/jira/browse/TUSCANY-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3209:
---
Component/s: OASIS Compliance
OASIS otest ASM_5032_TestCase has an incorrect endpoint uri
[
https://issues.apache.org/jira/browse/TUSCANY-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3231:
---
Component/s: OASIS Compliance
OASIS otest ASM_5029_TestCase fails as Tuscany is not noticing that
[
https://issues.apache.org/jira/browse/TUSCANY-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-3201:
---
Component/s: OASIS Compliance
OASIS otest ASM_5034_TestCase has invalid composte
On Fri, Aug 21, 2009 at 2:18 PM, Simon Lawssimonsl...@googlemail.com wrote:
Although perhaps we need more than that, for example i was about to
move TUSCANY-3231 there but its a Tuscany issue not an OASIS test
issue, do we need a component specifically for things in the OASIS
code?
...ant
Ok I've renamed it to OASIS Tests and we can use it for just issues
with the OASIS tests themselves, and i've been moving some JIRAs
there, i expect some may not be in the correct place but we can tweak
those as we find them. Do we need a component for compliance issues
with Tuscany so we can
Simon Laws wrote:
Ok I've renamed it to OASIS Tests and we can use it for just issues
with the OASIS tests themselves, and i've been moving some JIRAs
there, i expect some may not be in the correct place but we can tweak
those as we find them. Do we need a component for compliance issues
with
[
https://issues.apache.org/jira/browse/TUSCANY-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Edwards resolved TUSCANY-3230.
---
Resolution: Fixed
Fixed by the resolution for ASSEMBLY 171 in OASIS
- updated in OASIS
[
https://issues.apache.org/jira/browse/TUSCANY-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12746013#action_12746013
]
Mike Edwards commented on TUSCANY-3228:
---
This is a fault in the testcase materials.
[
https://issues.apache.org/jira/browse/TUSCANY-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12746020#action_12746020
]
Mike Edwards commented on TUSCANY-3226:
---
The testcase is valid and correct. There
[
https://issues.apache.org/jira/browse/TUSCANY-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12746030#action_12746030
]
Mike Edwards commented on TUSCANY-3224:
---
I agree, ASM50027 - ASM-TA-5031 is not
[
https://issues.apache.org/jira/browse/TUSCANY-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12746036#action_12746036
]
Mike Edwards commented on TUSCANY-3220:
---
Fixed by the resolution of ASSEMBLY 171
[
https://issues.apache.org/jira/browse/TUSCANY-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Edwards resolved TUSCANY-3220.
---
Resolution: Fixed
Update checked in to OASIS repository
OASIS clarrification required
[
https://issues.apache.org/jira/browse/TUSCANY-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12746045#action_12746045
]
Mike Edwards commented on TUSCANY-3219:
---
This is a failure in Tuscany.
In
[
https://issues.apache.org/jira/browse/TUSCANY-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12746054#action_12746054
]
Mike Edwards commented on TUSCANY-3218:
---
Yes, good catch. Issue raised in SCA
After a switch to another machine for various reasons (to v old FC5
and SUN JDK1.6.0_16) I'm seeing a failure in host-corba-jse when it's
testing if the orb has shut down. I see...
system-errException in thread quot;Thread-7quot;
java.lang.NullPointerException
at
See
http://hudson.zones.apache.org/hudson/job/Tuscany-2x/org.apache.tuscany.sca$itest-distribution-calculator-rmi/190/
46 matches
Mail list logo
