[ https://issues.apache.org/jira/browse/OAK-10413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761775#comment-17761775 ]
Marcel Reutegger commented on OAK-10413: ---------------------------------------- I'm able to reproduce when running tests in the same sequence like Jenkins does. Added the following test and then specified it on the command line with -Dtest=MyTest. {noformat} @RunWith(Suite.class) @Suite.SuiteClasses({ PurgeOldIndexVersionIT.class, LuceneIndexCommandIT.class, ReindexIT.class, DocumentStoreIndexerIT.class }) public class MyTest { } {noformat} Analyzing the heap dump... > DocumentStoreIndexerIT hanging > ------------------------------ > > Key: OAK-10413 > URL: https://issues.apache.org/jira/browse/OAK-10413 > Project: Jackrabbit Oak > Issue Type: Bug > Components: documentmk, run > Reporter: Julian Reschke > Priority: Major > > {noformat} > [INFO] Running org.apache.jackrabbit.oak.index.DocumentStoreIndexerIT > [WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM > 1. See FAQ web page and the dump file > /home/jenkins/jenkins-agent/workspace/Jackrabbit/jackrabbit-oak-trunk/oak-run/target/failsafe-reports/2023-08-22T13-46-32_129-jvmRun1.dumpstream > {noformat} > ...and then eventually times out. -- This message was sent by Atlassian Jira (v8.20.10#820010)