[
https://issues.apache.org/jira/browse/SLING-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940516#comment-14940516
]
Stefan Seifert commented on SLING-5067:
---------------------------------------
ah, ok? as suspected does not fail on "my machine".
what special process limit have you configured on your machine that produces
this problem?
i wonder why esp. this commit should be the source of new troubles.
the tests of which project exactly fail on your machine? sling-mock or
sling-mock-oak?
currently we do nothing more than closing the resource resolvers after a unit
test is done. the underlying oak repo is currently not closed explicitly (how
is this possible? i've not found a method for this on a first quick look.)
> sling-mock: "uniqueRoot()" to simplify creation and cleanup of unique root
> paths in repository
> ----------------------------------------------------------------------------------------------
>
> Key: SLING-5067
> URL: https://issues.apache.org/jira/browse/SLING-5067
> Project: Sling
> Issue Type: New Feature
> Components: Testing
> Affects Versions: Testing Sling Mock 1.5.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Labels: mocks
> Fix For: Testing Sling Mock Jackrabbit 1.0.0, Testing Sling Mock
> Oak 1.0.0, Testing Sling Mock 1.6.0
>
>
> when using resource resolver types JCR_JACKRABBIT and JCR_OAK unique root
> paths have to be used because the repository is not cleaned up after each
> run, and esp. if unit tests run in parallel.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
