Mike, Fair enough. I'll let them run for more than 30 minutes and see what happens.
How long does it take on your machine? I'm happy to signup for the wiki and add some extra information to http://wiki.apache.org/lucene-java/HowToContribute for folks wanting to tinker with Lucene. Do the Lucene developers typically run a subset of the test suite to make committing cheaper? Thanks, --Terry On Fri, Mar 7, 2014 at 5:52 AM, Michael McCandless < luc...@mikemccandless.com> wrote: > Unfortunately, some tests take a very long time, and the test infra > will print these HEARTBEAT messages notifying you that they are still > running. They should eventually finish? > > Mike McCandless > > http://blog.mikemccandless.com > > > On Thu, Mar 6, 2014 at 5:09 PM, Terry Smith <sheb...@gmail.com> wrote: > > I'm sure that I'm just missing something obvious but I'm having trouble > > getting the unit tests to run to completion on my laptop and was hoping > that > > someone would be kind enough to point me in the right direction. > > > > I've cloned the repository from GitHub > > (http://git.apache.org/lucene-solr.git) and checked out the latest > commit on > > branch_4x. > > > > commit 6e06247cec1410f32592bfd307c1020b814def06 > > > > Author: Robert Muir <rm...@apache.org> > > > > Date: Thu Mar 6 19:54:07 2014 +0000 > > > > > > disable slow solr tests in smoketester > > > > > > > > git-svn-id: > > https://svn.apache.org/repos/asf/lucene/dev/branches/branch_4x@1575025 > > 13f79535-47bb-0310-9956-ffa450edef68 > > > > > > Executing "ant clean test" from the top level directory of the project > shows > > the tests running but they seems to get stuck in loop with some stalled > > heartbeat messages. If I run the tests directly from lucene/ then they > > complete successfully after about 10 minutes. > > > > I'm using Java 6 under OS X (10.9.2). > > > > $ java -version > > > > java version "1.6.0_65" > > > > Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609) > > > > Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode) > > > > > > My terminal lists repeating stalled heartbeat messages like so: > > > > HEARTBEAT J2 PID(20104@onyx.local): 2014-03-06T16:53:35, stalled for > 2111s > > at: HdfsLockFactoryTest.testBasic > > > > HEARTBEAT J0 PID(20106@onyx.local): 2014-03-06T16:53:47, stalled for > 2108s > > at: TestSurroundQueryParser.testQueryParser > > > > HEARTBEAT J1 PID(20103@onyx.local): 2014-03-06T16:54:11, stalled for > 2167s > > at: TestRecoveryHdfs.testBuffering > > > > HEARTBEAT J3 PID(20105@onyx.local): 2014-03-06T16:54:23, stalled for > 2165s > > at: HdfsDirectoryTest.testEOF > > > > > > My machine does have 3 java processes chewing CPU, see attached jstack > dumps > > for more information. > > > > Should I expect the tests to complete on my platform? Do I need to > specify > > any special flags to give them more memory or to avoid any bad apples? > > > > Thanks in advance, > > > > --Terry > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: dev-h...@lucene.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >