On Tue, Jul 13, 2010 at 4:38 PM, Simon Laws <[email protected]> wrote: > On Tue, Jul 13, 2010 at 10:54 AM, Simon Laws <[email protected]> > wrote: >> On Mon, Jul 12, 2010 at 10:42 PM, ant elder <[email protected]> wrote: >>> On Sun, Jul 4, 2010 at 10:06 AM, Simon Laws <[email protected]> >>> wrote: >>> >>>>>> >>>>>> After today's updates we're down to 4.... >>>>>> >>>>>> Failed tests: >>>>>> testDummy(client_bws.BWS_2007_TestCase) >>>>>> testDummy(client_bws.BWS_2022_TestCase) >>>>>> testDummy(client_bws.BWS_2016_TestCase) >>>>>> testDummy(client_bws.BWS_5006_TestCase) >>>>>> >>>>>> Tests run: 74, Failures: 4, Errors: 0, Skipped: 37 >>>>>> >>> >>> I've got 5006 and 2016 fixed now. Looks like 5001 has started failing >>> now with some callback interface issue so its still three tests left >>> to fix. >>> >>> ...ant >>> >> >> I'm not seeing problems with 5001 so am down to two now.... >> >> Failed tests: >> testDummy(client_bws.BWS_2022_TestCase) >> testDummy(client_bws.BWS_2016_TestCase) >> >> Tests run: 74, Failures: 2, Errors: 0, Skipped: 37 >> >> Are the changes for 2016 committed? >> >> Simon >> >> >> -- >> Apache Tuscany committer: tuscany.apache.org >> Co-author of a book about Tuscany and SCA: tuscanyinaction.com >> > > I'm now seeing all the BWS tests passing! > > A full build to test the 2022 changes has made 2016 work somewhat > mysteriously.
2016 is one of the ones i'd fixed > mysteriously. I'm still not seeing failures in 5001 so would be > interested in hearing if anyone else is. > 5001 is still failing for me on the very latest otest and trunk code. I'll do some debugging. ...ant
