[ 
https://issues.apache.org/jira/browse/OAK-10413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761171#comment-17761171
 ] 

Mohit Kataria commented on OAK-10413:
-------------------------------------

Tested with following changes:
 # Added Eventual assertions: Jenkins job failed
 # Reverted changes  for OAK-10273 and OAK-10381 : jenkins job failed

So looks like this test was flaky from start. As there are also OOME in some 
runs, job's resource constraint may be leading to test failure. 

On local with sufficient resource tests are always passing.

> 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)

Reply via email to