Hi, I stuck at one of the test called "SampleFrameworks.CppFramework". It just stuck there forever while running without returning with test result.
In the test_output/SampleFrameworks/CppFramework/stderr, it stuck at: WARNING: Logging before InitGoogleLogging() is written to STDERR I0430 10:42:10.575156 445 master.cpp:263] Master started on 127.0.1.1:33891 I0430 10:42:10.575458 445 master.cpp:278] Master ID: 20120430104216842879-33891-420 I0430 10:42:10.575503 447 slave.cpp:200] Slave started on 127.0.1.1:33891 I0430 10:42:10.575525 447 slave.cpp:201] Slave resources: cpus=4; mem=0 I0430 10:42:10.575986 445 master.cpp:481] Elected as master! I0430 10:42:10.576141 447 slave.cpp:366] New master detected at [email protected]:33891 I0430 10:42:10.576315 445 master.cpp:524] Registering framework 20120430104216842879-33891-420-0000 at [email protected]:33891 I0430 10:42:10.576459 445 simple_allocator.cpp:46] Added framework 20120430104216842879-33891-420-0000 I0430 10:42:10.576649 445 master.cpp:842] Attempting to register slave 20120430104216842879-33891-420-0 at [email protected]:33891 I0430 10:42:10.576691 445 master.cpp:1058] Master now considering a slave at lh-PC:33891 as active I0430 10:42:10.576724 445 master.cpp:1594] Adding slave 20120430104216842879-33891-420-0 at lh-PC with cpus=4; mem=0 I0430 10:42:10.576884 445 simple_allocator.cpp:69] Added slave 20120430104216842879-33891-420-0 with cpus=4; mem=0 I0430 10:42:10.576897 447 slave.cpp:386] Registered with master; given slave ID 20120430104216842879-33891-420-0 Any help is appreciated. Thanks. Andy On Fri, Apr 27, 2012 at 2:39 PM, Charles Reiss <[email protected]>wrote: > On 4/27/12 12:27 PM, Hao Lin wrote: > >> And another problem while make check: >> >> I stuck at one of the test called "SampleFrameworks.**CppFramework". It >> just >> stuck there forever while running without returning with test result. >> > > It would be helpful to know what the logs in test_output/SampleFrameworks/ > **CppFramework say. > > - Charles > > > >> Thanks. >> >> Andy >> >> On Wed, Apr 25, 2012 at 8:05 PM, Benjamin Hindman <[email protected] >> >wrote: >> >> Hi Andy, >>> >>> This looks to do with the timeout that is used in that test. The timeout >>> only allows 1 second, but the test shows 2.6 seconds have elapsed (2625 >>> ms). You can easily check this by changing the Timeout values in >>> log_test.cpp to something greater than 1 second. >>> >>> I'm curious though, where are you running this? I've only seen this on >>> EC2 >>> and I'm curious if it has to do with hiccups from the virtualization. >>> >>> Ben. >>> >>> >>> On Wed, Apr 25, 2012 at 5:00 PM, Hao Lin <[email protected]> wrote: >>> >>> Hi, >>>> >>>> I have reached a problem in >>>> >>>> make check. >>>> >>>> It fails the one of test >>>> called CoordinatorTest.**MultipleAppendsNotLearnedFill: >>>> >>>> >>>> [ RUN ] CoordinatorTest.**MultipleAppendsNotLearnedFill >>>> tests/log_tests.cpp:860: Failure >>>> Value of: result.isSome() >>>> Actual: false >>>> Expected: true >>>> [ FAILED ] CoordinatorTest.**MultipleAppendsNotLearnedFill (2625 ms) >>>> [ RUN ] CoordinatorTest.Truncate >>>> /bin/bash: line 5: 15919 Segmentation fault ${dir}$tst >>>> FAIL: mesos-tests >>>> >>>> >>>> Any thought about the error is appreciated. >>>> >>>> Thanks. >>>> >>>> Andy >>>> >>>> >>> >> >> >> > > -- best wishes Hao Lin (林昊) Research Assistant School of Electrcial & Computer Eng Purdue University, West Lafayette, IN Personal Homepage: http://web.ics.purdue.edu/~lin116/
