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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2015/05/13 16:38:01 UTC
[jira] [Commented] (OAK-2771) Longevity tests in oak-run
[ https://issues.apache.org/jira/browse/OAK-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542018#comment-14542018 ]
Alex Parvulescu commented on OAK-2771:
--------------------------------------
linking to OAK-2870 as without it it is virtually impossible to create a SegmentNodeStore.
> Longevity tests in oak-run
> --------------------------
>
> Key: OAK-2771
> URL: https://issues.apache.org/jira/browse/OAK-2771
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run
> Reporter: Alex Parvulescu
> Priority: Minor
>
> How about adding a new category of tests in oak-run related to longevity testing. Around the SegmentMk bits I've seen emerge a new type of tests that setup an infinite sequence of operations waiting for a specific problem to surface and if the error doesn't happen, we have a never-ending test.
> Moreover running an IT test for a few hours is not reasonable on any of the current build platforms we have now.
> My proposal would be to add some of these tests to oak-run, provide a common way to instrument them and possibly expose some simple (http) UI to stop them once we think the results are satisfactory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)