Stefan L�tzkendorf wrote:

Hello, I know both problems,

the second one can be fixed with the patch I have posted as bug 28079.

Right, applied the patch. This lets the test succeed :)


The first one I've also observed unregularly, but have not idea.
both testcases are multi user tests and so I've thought Precondition Failed
is OK too.

Hmmm, maybe yes, augmenting the acceptable results might be good idea...


Oliver

Regards, Stefan

Oliver Zeigermann wrote:

Both

testsuite\junit\xmltestcases\functional\extra\multi-user\copy\copyDisjoint.xml

testsuite\junit\xmltestcases\functional\XML\SchemaCreateTestIdentColIdentResource.xml


fail very rarely because instead of the expected codes Created, No Content, Conflict [201, 204, 409], Forbidden 403 upon PUT is returned.


This error only occurs when used with more than one thread. This seems to be caused by VersionControlMethod line 158. I guess it is related to the history counter fix. I'd say it is no reason not to bring out the release candidate.

The problem with

testsuite\junit\xmltestcases\functional\proppatch\code\PropPatchDeleteDAVPropertyWithPropFindOnLockDiscovery.xml


is after LOCK upon PROPFIND all hrefs are preceeded by "/slide": <D:locktoken> <D:href>/slideopaquelocktoken%3Abc1fce93e3bcb2bdae8f5dbb7aa8c2d2</D:href> </D:locktoken>

                    <D:principal-URL>
<D:href>/slide/slide/users/unauthenticated</D:href>
                    </D:principal-URL>


The funny thing is this works in the HEAD branch.


Any ideas?

Oliver


Oliver Zeigermann wrote:


I have just run the functional tests run like

TProcessor.CMD -pattern *cases\\functional* -users 4 -iterations 4

on the release branch and three testcases failed:

testsuite\junit\xmltestcases\functional\extra\multi-user\copy\copyDisjoint.xml (occasionally)
testsuite\junit\xmltestcases\functional\proppatch\code\PropPatchDeleteDAVPropertyWithPropFindOnLockDiscovery.xml


testsuite\junit\xmltestcases\functional\XML\SchemaCreateTestIdentColIdentResource.xml


I will investigate this.


Oliver

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


.




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to