You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Amit Jain (JIRA)" <ji...@apache.org> on 2014/09/30 09:42:56 UTC

[jira] [Updated] (OAK-1716) Enable passing of a execution context to runTest in multi threaded runs

     [ https://issues.apache.org/jira/browse/OAK-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amit Jain updated OAK-1716:
---------------------------
    Fix Version/s:     (was: 1.1)
                   1.1.0

> Enable passing of a execution context to runTest in multi threaded runs
> -----------------------------------------------------------------------
>
>                 Key: OAK-1716
>                 URL: https://issues.apache.org/jira/browse/OAK-1716
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: bench
>    Affects Versions: 0.20
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>              Labels: concurrency, test
>             Fix For: 1.1.0
>
>
> Benchmark runner has support for specifying concurrency levels to execute the test with varying level of concurrency. In most cases the test case would be operating on a JCR session. With multi threaded runs we need a way to have jcr session bound to that thread of execution.
> To support that {{AbstractTest}} should provide a way for client to provide a executionContext object which sub classes can provide. That context would be managed per thread and passed to the runTest method if not null



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)