4 phpt test failures

I am getting the following 4 phpt test failure when I run
the tests on
the code in CURLEW (I also see them in the 1.2.0 released
code so It's
not specific to CURLEW).

SCA 004
SDO bug 10049
SDO bug 10842
SDO bug 8694

Can someone tell me if we are exepcting these to fail?

Simon


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

On May 11, 10:29 am, simonsl...googlemail.com wrote:
> I am getting the following 4 phpt test failure when I
run the tests on
> the code in CURLEW (I also see them in the 1.2.0
released code so It's
> not specific to CURLEW).
>
> SCA 004
> SDO bug 10049
> SDO bug 10842
> SDO bug 8694
>
> Can someone tell me if we are exepcting these to fail?

10842 and 8694 are time-bombed. If you look at the SKIPIF
section,
you'll see that they are skipped for releases <= 1.2.0.
Are you sure
you're working with code as in the repository or do you have
local
mods? Otherwise I don't know why they would even be running
for you.

The idea with these tests is that they demonstrate a
failure, and
should run clean when we get Tuscany fixes (test-driven
development?).
I think I've mentioned that I would like all SDO bugs to be
handled
this way, because  the turn-around time for Tuscany defects
is often
quite long, and if we get a fix but there's no reliable
testcase it
can take some time to reconstruct the problem. I've
time-bombed them
to make sure that they do get revisited at least for each
release.

If 10049 is failing that's a real problem though. Could you
post your
output diff for that one and SCA 004?


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

Comments in line

On 11 May, 10:49, cem <Caroline.Mayn...gmail.com> wrote:
> On May 11, 10:29 am, simonsl...googlemail.com wrote:
>
> > I am getting the following 4 phpt test failure
when I run the tests on
> > the code in CURLEW (I also see them in the 1.2.0
released code so It's
> > not specific to CURLEW).
>
> > SCA 004
> > SDO bug 10049
> > SDO bug 10842
> > SDO bug 8694
>
> > Can someone tell me if we are exepcting these to
fail?
>
> 10842 and 8694 are time-bombed. If you look at the
SKIPIF section,
> you'll see that they are skipped for releases <=
1.2.0. Are you sure
> you're working with code as in the repository or do you
have local
> mods? Otherwise I don't know why they would even be
running for you.
>
I'm running with the code from CURLEW. Which is >=1.2.0.
I'm not clear
from your comments whether these tests should or shouldn't
be
running. But they are running and failing in my case [3] and
[4].
> The idea with these tests is that they demonstrate a
failure, and
> should run clean when we get Tuscany fixes (test-driven
development?).
> I think I've mentioned that I would like all SDO bugs
to be handled
> this way, because  the turn-around time for Tuscany
defects is often
> quite long, and if we get a fix but there's no reliable
testcase it
> can take some time to reconstruct the problem. I've
time-bombed them
> to make sure that they do get revisited at least for
each release.
+1, sounds like a good approach to me
>
> If 10049 is failing that's a real problem though. Could
you post your
> output diff for that one and SCA 004?

[1] SCA 004

Fatal error: Uncaught exception
'SDO_DAS_XML_ParserException' with
message 'SDO_DAS_XML::create - Unable to parse the supplied
xsd file
1 parse error(s) occurred when parsing the file
'C:simonProjects
Tuscanyphpbranch-buildpeclsdoSCABindingssoap/soap/
2003-02-11.xsd':

I have just created a separate XML DAS Unit test to read
this schema
and it works fine. I'm still
investigating.

[2] 10049

---- EXPECTED OUTPUT
1
---- ACTUAL OUTPUT
1[Fri May 11 11:49:23 2007]  Script: 
'C:simonProjectsTuscanyphp
branch-buildpeclsdotestsSDOphptbug10049.php'
---- FAILED

[3] 10842

---- EXPECTED OUTPUT
Baby bear
Baby bear
Baby bear
---- ACTUAL OUTPUT
Baby bear
Baby bear
---- FAILED

[4] 8694

---- EXPECTED OUTPUT
1
1
---- ACTUAL OUTPUT

---- FAILED


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

On May 11, 11:58 am, simonsl...googlemail.com wrote:
> I'm running with the code from CURLEW. Which is
>=1.2.0. I'm not clear
> from your comments whether these tests should or
shouldn't be
> running. But they are running and failing in my case
[3] and [4].

They should be running if the SDO version number is >
1.2.0. Therefore
they will run (and fail) in CURLEW. If we build the next
release
before they get fixed (very likely), then the SKIPIF section
must be
updated accordingly as part of the release process. But you
said
originally that they also failed for you with 1.2.0. That's
what I
don't understand - they should be skipped there.

> [1] SCA 004

I'll leave this one to you for now.

>
> [2] 10049
>
> 1[Fri May 11 11:49:23 2007]  Script:
'C:simonProjectsTuscanyphpbranch-buildpeclsdotestsS
DOphptbug10049.php'

Congratulations, you've found a memory leak. You are running
in debug
mode. Strange though, because I also run in debug mode and I
don't see
a problem here.

The good news is that the test has worked.

I think you can turn the messages off with report_memleaks
in your
php.ini. But I do need to investigate what it is that's
leaking.


> [3] 10842
> [4] 8694

See above. Expected to fail, therefore should be skipped in
1.2.0. Can
you find out why they are not?


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

snip

> > [2] 10049
>
> > 1[Fri May 11 11:49:23 2007]  Script:
'C:simonProjectsTuscanyphpbranch-buildpeclsdotestsS
DOphptbug10049.php'
>
> Congratulations, you've found a memory leak. You are
running in debug
> mode. Strange though, because I also run in debug mode
and I don't see
> a problem here.
>
> The good news is that the test has worked.
>
> I think you can turn the messages off with
report_memleaks in your
> php.ini. But I do need to investigate what it is that's
leaking.

doh - i always forget about the mem leak message

>
> > [3] 10842
> > [4] 8694
>
> See above. Expected to fail, therefore should be
skipped in 1.2.0. Can
> you find out why they are not?

I just realize I ran the 1.2.0 php with the CURLEW sdo dll
due to the
way I have my PC configured. That's why they ran. Makes
sense now.

Simon


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

php004.phpt seems to be failing trying to resolve

<xs:import namespace = "http://schemas
.xmlsoap.org/wsdl/" />

Which is part of soap/soap/2003-02-11.xsd

However all the examples work OK so I can only guess this is
being
resolved successfully in other
scenarios. Is anyone else who has CURLEW checked out also
seeing
php004.phpt failing. I.e. I'm trying to work out if its a
fault in the
code or a fault with the environment in which I'm running
phpt tests.

Simon


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

On May 11, 1:06 pm, simonsl...googlemail.com wrote:
> php004.phpt seems to be failing trying to resolve
>
> <xs:import namespace = "http://schemas
.xmlsoap.org/wsdl/" />
>
> Which is part of soap/soap/2003-02-11.xsd
>

That import has no schemaLocation attribute, which concerns
me. Also,
remember that I removed the wsdl/soap schema files which
were hanging
around in the SCA root dir after being moved to the soap
binding dir.
So I wonder if there is a path problem?


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

On May 11, 12:51 pm, simonsl...googlemail.com wrote:

> doh - i always forget about the mem leak message

I wish I could do that too  


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

Hi Simon,

I've seen this kind of thing happen due to firewall
problems.  When
you run the tests from the commandline the firewall might
block
php.exe, but when you run samples in the browser it lets
apache.exe
through.  Might be a red herring.

On 11 May, 13:06, simonsl...googlemail.com wrote:
> php004.phpt seems to be failing trying to resolve
>
> <xs:import namespace = "http://schemas
.xmlsoap.org/wsdl/" />
>
> Which is part of soap/soap/2003-02-11.xsd
>
> However all the examples work OK so I can only guess
this is being
> resolved successfully in other
> scenarios. Is anyone else who has CURLEW checked out
also seeing
> php004.phpt failing. I.e. I'm trying to work out if its
a fault in the
> code or a fault with the environment in which I'm
running phpt tests.
>
> Simon


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---