POL_3002 can be ignored -- the test doesn't exist anymore.

POL_4015 and POL_4016 shouldn't be run, either. They test that an
exception is thrown when a runtime doesn't support directly attached
(4015) or externally attached (4016) policy sets. Since we support
both, both tests will fail. OASIS has addressed this by providing
different versions of the JUnit test runner (AllTests,
AllExtAttachTests, and AllDirectAttachTests.)

I'm surprised that you're both seeing 4033, 9022, and 9023 failing,
though. How are they failing?

Brent

On Wed, Jul 28, 2010 at 12:42 AM, Simon Laws <[email protected]> wrote:
> On Wed, Jul 28, 2010 at 8:27 AM, ant elder <[email protected]> wrote:
>> On Tue, Jul 27, 2010 at 5:00 PM, Simon Laws <[email protected]> 
>> wrote:
>>> On Tue, Jul 27, 2010 at 2:57 PM, kelvin goodson
>>> <[email protected]> wrote:
>>>> yes, that's it - I have fixed it
>>>>
>>>> Kelvin.
>>>>
>>>> On Tue, Jul 27, 2010 at 2:49 PM, Simon Laws <[email protected]> 
>>>> wrote:
>>>>> On Tue, Jul 27, 2010 at 2:23 PM, kelvin goodson
>>>
>>>
>>> Thanks Kelvin. I think we're looking good for Assembly again. I now
>>> get the following...
>>>
>>> Failed tests:
>>>  testDummy(client.ASM_12006_TestCase) - fails dues to
>>> externalAttachment elements for 10003
>>>  testDummy(client.ASM_8014_TestCase) - confidentiality.transport
>>>
>>> Tests run: 134, Failures: 2, Errors: 0, Skipped: 0
>>>
>>> Both of these issues are caused by stricter policy validation and I'll
>>> raise with OASIS.
>>>
>>
>> FWIW here's what i see for the other test suites:
>>
>> Java CI Failed tests:
>>  testDummy(client_javapojo.POJO_8012_TestCase)
>>  testDummy(client_javapojo.POJO_8020_TestCase)
>>  testDummy(client_javapojo.POJO_8017_TestCase)
>>  testDummy(client_javapojo.POJO_8003_TestCase)
>>  testDummy(client_javapojo.POJO_8016_TestCase)
>>
>> Tests run: 92, Failures: 5, Errors: 0, Skipped: 46
>>
>> Java CAA Failed tests:
>>  testDummy(client_javacaa.JCA_9013_TestCase)
>>  testDummy(client_javacaa.JCA_9016_TestCase)
>>  testDummy(client_javacaa.JCA_9011_TestCase)
>>  testDummy(client_javacaa.JCA_3013_TestCase)
>>  testDummy(client_javacaa.JCA_8006_TestCase)
>>  testDummy(client_javacaa.JCA_9009_TestCase)
>>  testDummy(client_javacaa.JCA_7006_TestCase)
>>  testDummy(client_javacaa.JCA_11010_TestCase)
>>  testDummy(client_javacaa.JCA_11009_TestCase)
>>  testDummy(client_javacaa.JCA_9006_TestCase)
>>  testDummy(client_javacaa.JCA_9010_TestCase)
>>  testDummy(client_javacaa.JCA_8001_TestCase)
>>  testDummy(client_javacaa.JCA_7004_TestCase)
>>  testDummy(client_javacaa.JCA_11012_TestCase)
>>  testDummy(client_javacaa.JCA_7005_TestCase)
>>  testDummy(client_javacaa.JCA_8011_TestCase)
>>  testDummy(client_javacaa.JCA_11015_TestCase)
>>  testDummy(client_javacaa.JCA_7002_TestCase)
>>  testDummy(client_javacaa.JCA_8007_TestCase)
>>  testDummy(client_javacaa.JCA_9012_TestCase)
>>  testDummy(client_javacaa.JCA_7003_TestCase)
>>  testDummy(client_javacaa.JCA_11011_TestCase)
>>  testDummy(client_javacaa.JCA_11014_TestCase)
>>  testDummy(client_javacaa.JCA_7001_TestCase)
>>  testDummy(client_javacaa.JCA_9008_TestCase)
>>  testDummy(client_javacaa.JCA_11013_TestCase)
>>  testDummy(client_javacaa.JCA_3014_TestCase)
>>  testDummy(client_javacaa.JCA_11016_TestCase)
>>
>> Tests run: 214, Failures: 28, Errors: 0, Skipped: 107
>>
>> Policy Failed tests:
>>  testDummy(client.POL_4016_TestCase)
>>  testDummy(client.POL_3002_TestCase)
>>  testDummy(client.POL_9023_TestCase)
>>  testDummy(client.POL_4015_TestCase)
>>  testDummy(client.POL_9022_TestCase)
>>  testDummy(client.POL_4033_TestCase)
>>
>> Tests run: 118, Failures: 6, Errors: 0, Skipped: 59
>>
>>   ...ant
>>
>
> Yep, I see the same. I've started looking at the JCI failures and a a
> number of these are also policy related.
>
> Simon
>
> --
> Apache Tuscany committer: tuscany.apache.org
> Co-author of a book about Tuscany and SCA: tuscanyinaction.com
>

Reply via email to