This cases might show that LogZooKeeperTest and MasterAuthorizationTest affect
each other.
joma@kopernikus-u:~/dev/programme/mesos/build/mesos/build$ make check
GTEST_FILTER="MasterAuthorizationTest.*"
Test Run OK.
joma@kopernikus-u:~/dev/programme/mesos/build/mesos/build$ make check
GTEST_FILTER="LogZooKeeper*:MasterAuthorizationTest.*"
Test Run NOK. Same parse error as reported.
P.S. Are those ZOO_ERROR in LogZooKeeperTest.LostZooKeeper expected to occur?
Just curious - as i stated elsewhere, log messages are highly overrated - test
result signals everything OK.
...
[==========] Running 15 tests from 2 test cases.
[----------] Global test environment set-up.
[----------] 2 tests from LogZooKeeperTest
[ RUN ] LogZooKeeperTest.WriteRead
[ OK ] LogZooKeeperTest.WriteRead (352 ms)
[ RUN ] LogZooKeeperTest.LostZooKeeper
2015-05-19
23:41:12,458:10099(0x2aae0b603700):ZOO_ERROR@handle_socket_error_msg@1721:
Socket [127.0.0.1:55588] zk retcode=-4, errno=112(Host is down): failed while
receiving a server response
2015-05-19
23:41:12,459:10099(0x2aae0b201700):ZOO_ERROR@handle_socket_error_msg@1721:
Socket [127.0.0.1:55588] zk retcode=-4, errno=112(Host is down): failed while
receiving a server response
[ OK ] LogZooKeeperTest.LostZooKeeper (83 ms)
[----------] 2 tests from LogZooKeeperTest (435 ms total)
[----------] 13 tests from MasterAuthorizationTest
[ RUN ] MasterAuthorizationTest.AuthorizedTask
[ OK ] MasterAuthorizationTest.AuthorizedTask (234 ms)
[ RUN ] MasterAuthorizationTest.UnauthorizedTask
[ OK ] MasterAuthorizationTest.UnauthorizedTask (163 ms)
[ RUN ] MasterAuthorizationTest.KillTask
[ OK ] MasterAuthorizationTest.KillTask (158 ms)
[ RUN ] MasterAuthorizationTest.SlaveRemoved
F0519 23:41:13.222724 10099 mesos.cpp:362] CHECK_SOME(parse): syntax error at line 1 near:
,"master\/valid_framework_to_executor_messages":0,"master\/valid_status_update_acknowledgements":0,"master\/valid_status_updates":0,"registrar\/queued_operations":0,"registrar\/registry_size_bytes":91,"registrar\/state_fetch_ms":37.902848,"registrar\/state_store_ms":15.227136,"registrar\/state_store_ms\/count":3,"registrar\/state_store_ms\/max":17.074944,"registrar\/state_store_ms\/min":15.227136,"registrar\/state_store_ms\/p50":15.872,"registrar\/state_store_ms\/p90":16.8343552,"registrar\/state_store_ms\/p95":16.9546496,"registrar\/state_store_ms\/p99":17.05088512,"registrar\/state_store_ms\/p999":17.072538112,"registrar\/state_store_ms\/p9999":17.0747034112,"scheduler\/event_queue_dispatches":0,"scheduler\/event_queue_messages":0,"system\/cpus_total":8,"system\/load_15min":0.57,"system\/load_1min":0.72,"system\/load_5min":0.67,"system\/mem_free_bytes":1133895680,"system\/mem_total_bytes":826
1
496832}
*** Check failure stack trace: ***
@ 0x2aadd7ff4800 google::LogMessage::Fail()
@ 0x2aadd7ff474c google::LogMessage::SendToLog()
@ 0x2aadd7ff414e google::LogMessage::Flush()
@ 0x2aadd7ff7062 google::LogMessageFatal::~LogMessageFatal()
@ 0xa26e98 _CheckFatal::~_CheckFatal()
@ 0xe60353 mesos::internal::tests::MesosTest::Metrics()
@ 0xd881f1
mesos::internal::tests::MasterAuthorizationTest_SlaveRemoved_Test::TestBody()
@ 0x113db61
testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@ 0x1138d1c
testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0x11210dd testing::Test::Run()
@ 0x1121800 testing::TestInfo::Run()
@ 0x1121d88 testing::TestCase::Run()
@ 0x1126a52 testing::internal::UnitTestImpl::RunAllTests()
@ 0x113e9d3
testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@ 0x1139a0d
testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0x112595e testing::UnitTest::Run()
@ 0xd2c87d main
@ 0x2aadda58cec5 (unknown)
@ 0x8f9869 (unknown)
make[3]: *** [check-local] Aborted (core dumped)
make[3]: Leaving directory
`/home/joma/entwicklung/programme/mesos/build/mesos/build/src'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory
`/home/joma/entwicklung/programme/mesos/build/mesos/build/src'
make[1]: *** [check] Error 2
make[1]: Leaving directory
`/home/joma/entwicklung/programme/mesos/build/mesos/build/src'
make: *** [check-recursive] Error 1
On 2015-05-19 22:03, Joerg Maurer wrote:
With "latest", do you refer to the latest revision in trunk?
Then no, I have tested against Release/Tag 0.22.1.
Should i try with latest?
On 2015-05-18 18:49, haosdent wrote:
@Joerg Maurer I could not reproduce your problems in CentOS. From this
ticket[https://issues.apache.org/jira/browse/MESOS-2744], @Colin Williams also
could not reproduce your problems in Ubuntu which kernel is 3.13.0-35-generic.
So could you sure the problem is exist in the latest code? Thank you
...
--
Best Regards,
Haosdent Huang
