[
https://issues.apache.org/jira/browse/JCR-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595276#action_12595276
]
anchela edited comment on JCR-1578 at 5/8/08 8:08 AM:
-----------------------------------------------------
fixed at rev 654542
since i never experience the bug in the past, i tried the following values for
the new
configuration parameter (second workspace name):
- same as default wsp.
- missing
- "security"
- "invalid" (thus a workspace name that does not exist)
- and obvious the 'expected' value "test"
the tests passed with all values (not-executable respectively)... hope that
fixes
the problem.
was (Author: anchela):
fixed at rev 654542
since i never experience the bug in the past, i tried the following values for
the new
configuration parameter (second workspace name):
- same as default wsp.
- missing
- "security"
- "invalid" (thus a workspace name that does not exist)
the tests passed with all values... hope that fixes the problem.
> Jcr2Spi: UpdateTest#testUpdateRemovesExtraProperty and
> #testUpdateAddsMissingSubtree fail occasionally
> ------------------------------------------------------------------------------------------------------
>
> Key: JCR-1578
> URL: https://issues.apache.org/jira/browse/JCR-1578
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-jcr2spi
> Reporter: angela
> Assignee: angela
> Priority: Minor
> Fix For: 1.5
>
>
> issue reported by jukka:
> Every now and then I see the following jcr2spi test failures on a
> clean checkout:
> Tests in error:
> testUpdateRemovesExtraProperty(org.apache.jackrabbit.jcr2spi.UpdateTest)
> testUpdateAddsMissingSubtree(org.apache.jackrabbit.jcr2spi.UpdateTest)
> The problem seems to be caused by the test cases automatically
> choosing the "security" workspace for the update test. The reason why
> the tests only fail occasionally is that currently the ordering of the
> string array returned by getAccessibleWorkspaceNames() is not
> deterministic.
> I can work around the issue by making
> RepositoryImpl.getWorkspaceNames() explicitly sort the returned array
> of names, but a more proper fix would probably be to ensure that the
> workspace selected by UpdateTest is useful for the test.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
