Even though the callstacks are empty and dunit-hangs.txt shows no tests, the 
file geode-core/build/repeatDistributedTest/repeatDistributedTest-progress.txt 
does show 683 lines -- half of those are "Starting" and half with one missing 
are "Completed" -- so I think there was a dunit test still running when the job 
timed out. I'm trying to track down a script to determine which test is missing 
a "Completed" line.

[ Full content available at: https://github.com/apache/geode/pull/3050 ]
This message was relayed via gitbox.apache.org for 
notifications@geode.apache.org

Reply via email to