You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Qian Zhang <zh...@gmail.com> on 2015/06/01 17:20:35 UTC
Failed to "make check" and run example framework
Hi,
I followed the exact steps in http://mesos.apache.org/gettingstarted/ to
try Mesos, what I am using is a RHEL 6.5 x86_64 virtual machine. But "make
check" failed:
[----------] 1 test from PerfEventIsolatorTest
[ RUN ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
F0601 22:45:27.851017 12655 isolator_tests.cpp:710] CHECK_SOME(isolator):
Perf is not supported
*** Check failure stack trace: ***
@ 0x7ffe4fa7dd60 google::LogMessage::Fail()
@ 0x7ffe4fa7dcb9 google::LogMessage::SendToLog()
@ 0x7ffe4fa7d697 google::LogMessage::Flush()
@ 0x7ffe4fa8061f google::LogMessageFatal::~LogMessageFatal()
@ 0x97fe94 _CheckFatal::~_CheckFatal()
@ 0xbf7829
mesos::internal::tests::PerfEventIsolatorTest_ROOT_CGROUPS_Sample_Test::TestBody()
@ 0x10e5fa5
testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@ 0x10e0abe
testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0x10c783e testing::Test::Run()
@ 0x10c8078 testing::TestInfo::Run()
@ 0x10c86ac testing::TestCase::Run()
@ 0x10cda39 testing::internal::UnitTestImpl::RunAllTests()
@ 0x10e71f9
testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@ 0x10e1899
testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0x10cc5c1 testing::UnitTest::Run()
@ 0xc9fe96 main
@ 0x7ffe4bb21d1d __libc_start_main
@ 0x85ba69 (unknown)
I0601 22:45:29.976155 14327 exec.cpp:450] Slave exited, but framework has
checkpointing enabled. Waiting 15mins to reconnect with slave
20150601-224223-2574952640-39385-12655-S0
make[3]: *** [check-local] Aborted (core dumped)
make[3]: Leaving directory `/root/mesos-0.22.1/build/src'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/root/mesos-0.22.1/build/src'
make[1]: *** [check] Error 2
make[1]: Leaving directory `/root/mesos-0.22.1/build/src'
make: *** [check-recursive] Error 1
[root@mesos build]# echo $?
2
And the example C++ framework also failed:
# ./src/test-framework --master=127.0.0.1:5050
I0601 23:02:44.646636 14828 sched.cpp:157] Version: 0.22.1
I0601 23:02:44.662256 14849 sched.cpp:254] New master detected at
master@127.0.0.1:5050
I0601 23:02:44.664237 14849 sched.cpp:264] No credentials provided.
Attempting to register without authentication
I0601 23:02:44.670964 14853 sched.cpp:448] Framework registered with
20150601-225015-16777343-5050-14668-0000
Registered!
Received offer 20150601-225015-16777343-5050-14668-O0 with cpus(*):4;
mem(*):2806; disk(*):40810; ports(*):[31000-32000]
Launching task 0 using offer 20150601-225015-16777343-5050-14668-O0
Launching task 1 using offer 20150601-225015-16777343-5050-14668-O0
Launching task 2 using offer 20150601-225015-16777343-5050-14668-O0
Launching task 3 using offer 20150601-225015-16777343-5050-14668-O0
Task 0 is in state TASK_LOST
Aborting because task 0 is in unexpected state TASK_LOST with reason 1 from
source 1 with message 'Executor terminated'
I0601 23:02:44.880982 14848 sched.cpp:1623] Asked to abort the driver
I0601 23:02:44.881239 14848 sched.cpp:856] Aborting framework
'20150601-225015-16777343-5050-14668-0000'
I0601 23:02:44.881921 14828 sched.cpp:1589] Asked to stop the driver
Any help will be appreciated, thanks!
Re: Failed to "make check" and run example framework
Posted by Qian Zhang <zh...@gmail.com>.
Got it, thanks Ian!
2015-06-03 2:28 GMT+08:00 Ian Downes <id...@twitter.com>:
> This is another test that uses the perf_event isolator, please disable
> that test too with
> GTEST_FILTER="-Perf*:-UserCgroupIsolatorTest*UserCgroup"
>
> See here for more documentation on skipping tests:
>
> https://code.google.com/p/googletest/wiki/V1_6_AdvancedGuide#Running_a_Subset_of_the_Tests
>
> This will all be automatically handled when the correct environment
> detection is implemented.
>
>
> On Mon, Jun 1, 2015 at 7:25 PM, Qian Zhang <zh...@gmail.com> wrote:
>
>> I reran the check with "GTEST_FILTER="-Perf*" make check", but it failed
>> again in another place:
>>
>> [ RUN ] UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
>> -bash: /sys/fs/cgroup/cpu/mesos/container/cgroup.procs: No such file or
>> directory
>> mkdir: cannot create directory `/sys/fs/cgroup/cpu/mesos/container/user':
>> No such file or directory
>> ../../src/tests/isolator_tests.cpp:1127: Failure
>> Value of: os::system( "su - " + UNPRIVILEGED_USERNAME + " -c 'mkdir " +
>> path::join(flags.cgroups_hierarchy, userCgroup) + "'")
>> Actual: 256
>> Expected: 0
>> -bash: /sys/fs/cgroup/cpu/mesos/container/user/cgroup.procs: No such file
>> or directory
>> ../../src/tests/isolator_tests.cpp:1136: Failure
>> Value of: os::system( "su - " + UNPRIVILEGED_USERNAME + " -c 'echo $$ >"
>> + path::join(flags.cgroups_hierarchy, userCgroup, "cgroup.procs") + "'")
>> Actual: 256
>> Expected: 0
>> -bash: /sys/fs/cgroup/cpuacct/mesos/container/cgroup.procs: No such file
>> or directory
>> mkdir: cannot create directory
>> `/sys/fs/cgroup/cpuacct/mesos/container/user': No such file or directory
>> ../../src/tests/isolator_tests.cpp:1127: Failure
>> Value of: os::system( "su - " + UNPRIVILEGED_USERNAME + " -c 'mkdir " +
>> path::join(flags.cgroups_hierarchy, userCgroup) + "'")
>> Actual: 256
>> Expected: 0
>> -bash: /sys/fs/cgroup/cpuacct/mesos/container/user/cgroup.procs: No such
>> file or directory
>> ../../src/tests/isolator_tests.cpp:1136: Failure
>> Value of: os::system( "su - " + UNPRIVILEGED_USERNAME + " -c 'echo $$ >"
>> + path::join(flags.cgroups_hierarchy, userCgroup, "cgroup.procs") + "'")
>> Actual: 256
>> Expected: 0
>> [ FAILED ] UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup, where
>> TypeParam = mesos::internal::slave::CgroupsCpushareIsolatorProcess (443 ms)
>> [----------] 1 test from UserCgroupIsolatorTest/1 (443 ms total)
>>
>> [----------] 1 test from UserCgroupIsolatorTest/2, where TypeParam =
>> mesos::internal::slave::CgroupsPerfEventIsolatorProcess
>> userdel: user 'mesos.test.unprivileged.user' does not exist
>> [ RUN ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup
>> F0602 10:13:49.849755 4279 isolator_tests.cpp:1054]
>> CHECK_SOME(isolator): Perf is not supported
>> *** Check failure stack trace: ***
>> 2015-06-02
>> 10:13:49,863:4279(0x7fd4cf5fe700):ZOO_ERROR@handle_socket_error_msg@1697:
>> Socket [127.0.0.1:45737] zk retcode=-4, errno=111(Connection refused):
>> server refused to accept the client
>> @ 0x7fd569fc2d60 google::LogMessage::Fail()
>> @ 0x7fd569fc2cb9 google::LogMessage::SendToLog()
>> @ 0x7fd569fc2697 google::LogMessage::Flush()
>> @ 0x7fd569fc561f google::LogMessageFatal::~LogMessageFatal()
>> @ 0x97fe94 _CheckFatal::~_CheckFatal()
>> @ 0xc10e55
>> mesos::internal::tests::UserCgroupIsolatorTest_ROOT_CGROUPS_UserCgroup_Test<>::TestBody()
>> @ 0x10e5fa5
>> testing::internal::HandleSehExceptionsInMethodIfSupported<>()
>> @ 0x10e0abe
>> testing::internal::HandleExceptionsInMethodIfSupported<>()
>> @ 0x10c783e testing::Test::Run()
>> @ 0x10c8078 testing::TestInfo::Run()
>> @ 0x10c86ac testing::TestCase::Run()
>> @ 0x10cda39 testing::internal::UnitTestImpl::RunAllTests()
>> @ 0x10e71f9
>> testing::internal::HandleSehExceptionsInMethodIfSupported<>()
>> @ 0x10e1899
>> testing::internal::HandleExceptionsInMethodIfSupported<>()
>> @ 0x10cc5c1 testing::UnitTest::Run()
>> @ 0xc9fe96 main
>> @ 0x38d141ed1d (unknown)
>> @ 0x85ba69 (unknown)
>> I0602 10:13:52.680408 5947 exec.cpp:450] Slave exited, but framework has
>> checkpointing enabled. Waiting 15mins to reconnect with slave
>> 20150602-101045-2574952640-43322-4279-S0
>> make[3]: *** [check-local] Aborted (core dumped)
>> make[3]: Leaving directory `/root/mesos-0.22.1/build/src'
>> make[2]: *** [check-am] Error 2
>> make[2]: Leaving directory `/root/mesos-0.22.1/build/src'
>> make[1]: *** [check] Error 2
>> make[1]: Leaving directory `/root/mesos-0.22.1/build/src'
>> make: *** [check-recursive] Error 1
>>
>>
>
Re: Failed to "make check" and run example framework
Posted by Ian Downes <id...@twitter.com>.
This is another test that uses the perf_event isolator, please disable that
test too with
GTEST_FILTER="-Perf*:-UserCgroupIsolatorTest*UserCgroup"
See here for more documentation on skipping tests:
https://code.google.com/p/googletest/wiki/V1_6_AdvancedGuide#Running_a_Subset_of_the_Tests
This will all be automatically handled when the correct environment
detection is implemented.
On Mon, Jun 1, 2015 at 7:25 PM, Qian Zhang <zh...@gmail.com> wrote:
> I reran the check with "GTEST_FILTER="-Perf*" make check", but it failed
> again in another place:
>
> [ RUN ] UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
> -bash: /sys/fs/cgroup/cpu/mesos/container/cgroup.procs: No such file or
> directory
> mkdir: cannot create directory `/sys/fs/cgroup/cpu/mesos/container/user':
> No such file or directory
> ../../src/tests/isolator_tests.cpp:1127: Failure
> Value of: os::system( "su - " + UNPRIVILEGED_USERNAME + " -c 'mkdir " +
> path::join(flags.cgroups_hierarchy, userCgroup) + "'")
> Actual: 256
> Expected: 0
> -bash: /sys/fs/cgroup/cpu/mesos/container/user/cgroup.procs: No such file
> or directory
> ../../src/tests/isolator_tests.cpp:1136: Failure
> Value of: os::system( "su - " + UNPRIVILEGED_USERNAME + " -c 'echo $$ >" +
> path::join(flags.cgroups_hierarchy, userCgroup, "cgroup.procs") + "'")
> Actual: 256
> Expected: 0
> -bash: /sys/fs/cgroup/cpuacct/mesos/container/cgroup.procs: No such file
> or directory
> mkdir: cannot create directory
> `/sys/fs/cgroup/cpuacct/mesos/container/user': No such file or directory
> ../../src/tests/isolator_tests.cpp:1127: Failure
> Value of: os::system( "su - " + UNPRIVILEGED_USERNAME + " -c 'mkdir " +
> path::join(flags.cgroups_hierarchy, userCgroup) + "'")
> Actual: 256
> Expected: 0
> -bash: /sys/fs/cgroup/cpuacct/mesos/container/user/cgroup.procs: No such
> file or directory
> ../../src/tests/isolator_tests.cpp:1136: Failure
> Value of: os::system( "su - " + UNPRIVILEGED_USERNAME + " -c 'echo $$ >" +
> path::join(flags.cgroups_hierarchy, userCgroup, "cgroup.procs") + "'")
> Actual: 256
> Expected: 0
> [ FAILED ] UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup, where
> TypeParam = mesos::internal::slave::CgroupsCpushareIsolatorProcess (443 ms)
> [----------] 1 test from UserCgroupIsolatorTest/1 (443 ms total)
>
> [----------] 1 test from UserCgroupIsolatorTest/2, where TypeParam =
> mesos::internal::slave::CgroupsPerfEventIsolatorProcess
> userdel: user 'mesos.test.unprivileged.user' does not exist
> [ RUN ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup
> F0602 10:13:49.849755 4279 isolator_tests.cpp:1054] CHECK_SOME(isolator):
> Perf is not supported
> *** Check failure stack trace: ***
> 2015-06-02
> 10:13:49,863:4279(0x7fd4cf5fe700):ZOO_ERROR@handle_socket_error_msg@1697:
> Socket [127.0.0.1:45737] zk retcode=-4, errno=111(Connection refused):
> server refused to accept the client
> @ 0x7fd569fc2d60 google::LogMessage::Fail()
> @ 0x7fd569fc2cb9 google::LogMessage::SendToLog()
> @ 0x7fd569fc2697 google::LogMessage::Flush()
> @ 0x7fd569fc561f google::LogMessageFatal::~LogMessageFatal()
> @ 0x97fe94 _CheckFatal::~_CheckFatal()
> @ 0xc10e55
> mesos::internal::tests::UserCgroupIsolatorTest_ROOT_CGROUPS_UserCgroup_Test<>::TestBody()
> @ 0x10e5fa5
> testing::internal::HandleSehExceptionsInMethodIfSupported<>()
> @ 0x10e0abe
> testing::internal::HandleExceptionsInMethodIfSupported<>()
> @ 0x10c783e testing::Test::Run()
> @ 0x10c8078 testing::TestInfo::Run()
> @ 0x10c86ac testing::TestCase::Run()
> @ 0x10cda39 testing::internal::UnitTestImpl::RunAllTests()
> @ 0x10e71f9
> testing::internal::HandleSehExceptionsInMethodIfSupported<>()
> @ 0x10e1899
> testing::internal::HandleExceptionsInMethodIfSupported<>()
> @ 0x10cc5c1 testing::UnitTest::Run()
> @ 0xc9fe96 main
> @ 0x38d141ed1d (unknown)
> @ 0x85ba69 (unknown)
> I0602 10:13:52.680408 5947 exec.cpp:450] Slave exited, but framework has
> checkpointing enabled. Waiting 15mins to reconnect with slave
> 20150602-101045-2574952640-43322-4279-S0
> make[3]: *** [check-local] Aborted (core dumped)
> make[3]: Leaving directory `/root/mesos-0.22.1/build/src'
> make[2]: *** [check-am] Error 2
> make[2]: Leaving directory `/root/mesos-0.22.1/build/src'
> make[1]: *** [check] Error 2
> make[1]: Leaving directory `/root/mesos-0.22.1/build/src'
> make: *** [check-recursive] Error 1
>
>
Re: Failed to "make check" and run example framework
Posted by Qian Zhang <zh...@gmail.com>.
I reran the check with "GTEST_FILTER="-Perf*" make check", but it failed
again in another place:
[ RUN ] UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
-bash: /sys/fs/cgroup/cpu/mesos/container/cgroup.procs: No such file or
directory
mkdir: cannot create directory `/sys/fs/cgroup/cpu/mesos/container/user':
No such file or directory
../../src/tests/isolator_tests.cpp:1127: Failure
Value of: os::system( "su - " + UNPRIVILEGED_USERNAME + " -c 'mkdir " +
path::join(flags.cgroups_hierarchy, userCgroup) + "'")
Actual: 256
Expected: 0
-bash: /sys/fs/cgroup/cpu/mesos/container/user/cgroup.procs: No such file
or directory
../../src/tests/isolator_tests.cpp:1136: Failure
Value of: os::system( "su - " + UNPRIVILEGED_USERNAME + " -c 'echo $$ >" +
path::join(flags.cgroups_hierarchy, userCgroup, "cgroup.procs") + "'")
Actual: 256
Expected: 0
-bash: /sys/fs/cgroup/cpuacct/mesos/container/cgroup.procs: No such file or
directory
mkdir: cannot create directory
`/sys/fs/cgroup/cpuacct/mesos/container/user': No such file or directory
../../src/tests/isolator_tests.cpp:1127: Failure
Value of: os::system( "su - " + UNPRIVILEGED_USERNAME + " -c 'mkdir " +
path::join(flags.cgroups_hierarchy, userCgroup) + "'")
Actual: 256
Expected: 0
-bash: /sys/fs/cgroup/cpuacct/mesos/container/user/cgroup.procs: No such
file or directory
../../src/tests/isolator_tests.cpp:1136: Failure
Value of: os::system( "su - " + UNPRIVILEGED_USERNAME + " -c 'echo $$ >" +
path::join(flags.cgroups_hierarchy, userCgroup, "cgroup.procs") + "'")
Actual: 256
Expected: 0
[ FAILED ] UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup, where
TypeParam = mesos::internal::slave::CgroupsCpushareIsolatorProcess (443 ms)
[----------] 1 test from UserCgroupIsolatorTest/1 (443 ms total)
[----------] 1 test from UserCgroupIsolatorTest/2, where TypeParam =
mesos::internal::slave::CgroupsPerfEventIsolatorProcess
userdel: user 'mesos.test.unprivileged.user' does not exist
[ RUN ] UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup
F0602 10:13:49.849755 4279 isolator_tests.cpp:1054] CHECK_SOME(isolator):
Perf is not supported
*** Check failure stack trace: ***
2015-06-02
10:13:49,863:4279(0x7fd4cf5fe700):ZOO_ERROR@handle_socket_error_msg@1697:
Socket [127.0.0.1:45737] zk retcode=-4, errno=111(Connection refused):
server refused to accept the client
@ 0x7fd569fc2d60 google::LogMessage::Fail()
@ 0x7fd569fc2cb9 google::LogMessage::SendToLog()
@ 0x7fd569fc2697 google::LogMessage::Flush()
@ 0x7fd569fc561f google::LogMessageFatal::~LogMessageFatal()
@ 0x97fe94 _CheckFatal::~_CheckFatal()
@ 0xc10e55
mesos::internal::tests::UserCgroupIsolatorTest_ROOT_CGROUPS_UserCgroup_Test<>::TestBody()
@ 0x10e5fa5
testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@ 0x10e0abe
testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0x10c783e testing::Test::Run()
@ 0x10c8078 testing::TestInfo::Run()
@ 0x10c86ac testing::TestCase::Run()
@ 0x10cda39 testing::internal::UnitTestImpl::RunAllTests()
@ 0x10e71f9
testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@ 0x10e1899
testing::internal::HandleExceptionsInMethodIfSupported<>()
@ 0x10cc5c1 testing::UnitTest::Run()
@ 0xc9fe96 main
@ 0x38d141ed1d (unknown)
@ 0x85ba69 (unknown)
I0602 10:13:52.680408 5947 exec.cpp:450] Slave exited, but framework has
checkpointing enabled. Waiting 15mins to reconnect with slave
20150602-101045-2574952640-43322-4279-S0
make[3]: *** [check-local] Aborted (core dumped)
make[3]: Leaving directory `/root/mesos-0.22.1/build/src'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/root/mesos-0.22.1/build/src'
make[1]: *** [check] Error 2
make[1]: Leaving directory `/root/mesos-0.22.1/build/src'
make: *** [check-recursive] Error 1
Re: Failed to "make check" and run example framework
Posted by Ian Downes <id...@twitter.com>.
Perf is specific to the kernel version and different versions have
different flags and output formats. Specifically, the code requires a
kernel release >= 2.6.39 but you're running a 2.6.32 kernel: your version
of perf is not currently supported and you should skip those tests. The
only effect of this is that you cannot use the optional perf_event isolator.
On Mon, Jun 1, 2015 at 5:03 PM, Qian Zhang <zh...@gmail.com> wrote:
> Thanks Haosdent and Ian.
>
> But in my machine, I already have perf installed, so I am not sure why
> those test cases still failed.
> # rpm -qa | grep perf
> perf-2.6.32-431.el6.x86_64
> # which perf
> /usr/bin/perf
>
> And can you please let me know why my example C++ framework works as
> normal? I see the following message:
> Task 0 is in state TASK_LOST
> Aborting because task 0 is in unexpected state TASK_LOST with reason 1
> from source 1 with message 'Executor terminated'
> It seems task is in an unexpected state, right? And after
> "./src/test-framework --master=127.0.0.1:5050" is executed, I ran "echo
> $?", and its output is 1 which means something wrong, otherwise "echo $?"
> should output 0, right?
>
>
>
Re: Failed to "make check" and run example framework
Posted by Qian Zhang <zh...@gmail.com>.
Thanks Haosdent and Ian.
But in my machine, I already have perf installed, so I am not sure why
those test cases still failed.
# rpm -qa | grep perf
perf-2.6.32-431.el6.x86_64
# which perf
/usr/bin/perf
And can you please let me know why my example C++ framework works as
normal? I see the following message:
Task 0 is in state TASK_LOST
Aborting because task 0 is in unexpected state TASK_LOST with reason 1
from source 1 with message 'Executor terminated'
It seems task is in an unexpected state, right? And after
"./src/test-framework --master=127.0.0.1:5050" is executed, I ran "echo
$?", and its output is 1 which means something wrong, otherwise "echo $?"
should output 0, right?
Re: Failed to "make check" and run example framework
Posted by Ian Downes <id...@twitter.com>.
Correct, this is because you don't have perf installed on your host. It is
only needed for a particular isolator (perf_event) so you can install perf
if you want to use it or simple skip these tests using
"GTEST_FILTER="-Perf*" make check" if you don't need it.
I've filed https://issues.apache.org/jira/browse/MESOS-2789 to
automatically detect and skip these tests.
On Mon, Jun 1, 2015 at 9:53 AM, haosdent <ha...@gmail.com> wrote:
> Hi, @Qian Zhang. I think
>
> ```
> # ./src/test-framework --master=127.0.0.1:5050
> ```
> works as normal.
>
> For the `make check`, I think the failed test case is because your machine
> don't install some test dependency, it should not affect your normal use.
>
> On Mon, Jun 1, 2015 at 11:20 PM, Qian Zhang <zh...@gmail.com> wrote:
>
>> Hi,
>>
>> I followed the exact steps in http://mesos.apache.org/gettingstarted/ to
>> try Mesos, what I am using is a RHEL 6.5 x86_64 virtual machine. But "make
>> check" failed:
>> [----------] 1 test from PerfEventIsolatorTest
>> [ RUN ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
>> F0601 22:45:27.851017 12655 isolator_tests.cpp:710] CHECK_SOME(isolator):
>> Perf is not supported
>> *** Check failure stack trace: ***
>> @ 0x7ffe4fa7dd60 google::LogMessage::Fail()
>> @ 0x7ffe4fa7dcb9 google::LogMessage::SendToLog()
>> @ 0x7ffe4fa7d697 google::LogMessage::Flush()
>> @ 0x7ffe4fa8061f google::LogMessageFatal::~LogMessageFatal()
>> @ 0x97fe94 _CheckFatal::~_CheckFatal()
>> @ 0xbf7829
>> mesos::internal::tests::PerfEventIsolatorTest_ROOT_CGROUPS_Sample_Test::TestBody()
>> @ 0x10e5fa5
>> testing::internal::HandleSehExceptionsInMethodIfSupported<>()
>> @ 0x10e0abe
>> testing::internal::HandleExceptionsInMethodIfSupported<>()
>> @ 0x10c783e testing::Test::Run()
>> @ 0x10c8078 testing::TestInfo::Run()
>> @ 0x10c86ac testing::TestCase::Run()
>> @ 0x10cda39 testing::internal::UnitTestImpl::RunAllTests()
>> @ 0x10e71f9
>> testing::internal::HandleSehExceptionsInMethodIfSupported<>()
>> @ 0x10e1899
>> testing::internal::HandleExceptionsInMethodIfSupported<>()
>> @ 0x10cc5c1 testing::UnitTest::Run()
>> @ 0xc9fe96 main
>> @ 0x7ffe4bb21d1d __libc_start_main
>> @ 0x85ba69 (unknown)
>> I0601 22:45:29.976155 14327 exec.cpp:450] Slave exited, but framework has
>> checkpointing enabled. Waiting 15mins to reconnect with slave
>> 20150601-224223-2574952640-39385-12655-S0
>> make[3]: *** [check-local] Aborted (core dumped)
>> make[3]: Leaving directory `/root/mesos-0.22.1/build/src'
>> make[2]: *** [check-am] Error 2
>> make[2]: Leaving directory `/root/mesos-0.22.1/build/src'
>> make[1]: *** [check] Error 2
>> make[1]: Leaving directory `/root/mesos-0.22.1/build/src'
>> make: *** [check-recursive] Error 1
>> [root@mesos build]# echo $?
>> 2
>>
>>
>> And the example C++ framework also failed:
>> # ./src/test-framework --master=127.0.0.1:5050
>> I0601 23:02:44.646636 14828 sched.cpp:157] Version: 0.22.1
>> I0601 23:02:44.662256 14849 sched.cpp:254] New master detected at
>> master@127.0.0.1:5050
>> I0601 23:02:44.664237 14849 sched.cpp:264] No credentials provided.
>> Attempting to register without authentication
>> I0601 23:02:44.670964 14853 sched.cpp:448] Framework registered with
>> 20150601-225015-16777343-5050-14668-0000
>> Registered!
>> Received offer 20150601-225015-16777343-5050-14668-O0 with cpus(*):4;
>> mem(*):2806; disk(*):40810; ports(*):[31000-32000]
>> Launching task 0 using offer 20150601-225015-16777343-5050-14668-O0
>> Launching task 1 using offer 20150601-225015-16777343-5050-14668-O0
>> Launching task 2 using offer 20150601-225015-16777343-5050-14668-O0
>> Launching task 3 using offer 20150601-225015-16777343-5050-14668-O0
>> Task 0 is in state TASK_LOST
>> Aborting because task 0 is in unexpected state TASK_LOST with reason 1
>> from source 1 with message 'Executor terminated'
>> I0601 23:02:44.880982 14848 sched.cpp:1623] Asked to abort the driver
>> I0601 23:02:44.881239 14848 sched.cpp:856] Aborting framework
>> '20150601-225015-16777343-5050-14668-0000'
>> I0601 23:02:44.881921 14828 sched.cpp:1589] Asked to stop the driver
>>
>>
>>
>> Any help will be appreciated, thanks!
>>
>>
>
>
> --
> Best Regards,
> Haosdent Huang
>
Re: Failed to "make check" and run example framework
Posted by haosdent <ha...@gmail.com>.
Hi, @Qian Zhang. I think
```
# ./src/test-framework --master=127.0.0.1:5050
```
works as normal.
For the `make check`, I think the failed test case is because your machine
don't install some test dependency, it should not affect your normal use.
On Mon, Jun 1, 2015 at 11:20 PM, Qian Zhang <zh...@gmail.com> wrote:
> Hi,
>
> I followed the exact steps in http://mesos.apache.org/gettingstarted/ to
> try Mesos, what I am using is a RHEL 6.5 x86_64 virtual machine. But "make
> check" failed:
> [----------] 1 test from PerfEventIsolatorTest
> [ RUN ] PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> F0601 22:45:27.851017 12655 isolator_tests.cpp:710] CHECK_SOME(isolator):
> Perf is not supported
> *** Check failure stack trace: ***
> @ 0x7ffe4fa7dd60 google::LogMessage::Fail()
> @ 0x7ffe4fa7dcb9 google::LogMessage::SendToLog()
> @ 0x7ffe4fa7d697 google::LogMessage::Flush()
> @ 0x7ffe4fa8061f google::LogMessageFatal::~LogMessageFatal()
> @ 0x97fe94 _CheckFatal::~_CheckFatal()
> @ 0xbf7829
> mesos::internal::tests::PerfEventIsolatorTest_ROOT_CGROUPS_Sample_Test::TestBody()
> @ 0x10e5fa5
> testing::internal::HandleSehExceptionsInMethodIfSupported<>()
> @ 0x10e0abe
> testing::internal::HandleExceptionsInMethodIfSupported<>()
> @ 0x10c783e testing::Test::Run()
> @ 0x10c8078 testing::TestInfo::Run()
> @ 0x10c86ac testing::TestCase::Run()
> @ 0x10cda39 testing::internal::UnitTestImpl::RunAllTests()
> @ 0x10e71f9
> testing::internal::HandleSehExceptionsInMethodIfSupported<>()
> @ 0x10e1899
> testing::internal::HandleExceptionsInMethodIfSupported<>()
> @ 0x10cc5c1 testing::UnitTest::Run()
> @ 0xc9fe96 main
> @ 0x7ffe4bb21d1d __libc_start_main
> @ 0x85ba69 (unknown)
> I0601 22:45:29.976155 14327 exec.cpp:450] Slave exited, but framework has
> checkpointing enabled. Waiting 15mins to reconnect with slave
> 20150601-224223-2574952640-39385-12655-S0
> make[3]: *** [check-local] Aborted (core dumped)
> make[3]: Leaving directory `/root/mesos-0.22.1/build/src'
> make[2]: *** [check-am] Error 2
> make[2]: Leaving directory `/root/mesos-0.22.1/build/src'
> make[1]: *** [check] Error 2
> make[1]: Leaving directory `/root/mesos-0.22.1/build/src'
> make: *** [check-recursive] Error 1
> [root@mesos build]# echo $?
> 2
>
>
> And the example C++ framework also failed:
> # ./src/test-framework --master=127.0.0.1:5050
> I0601 23:02:44.646636 14828 sched.cpp:157] Version: 0.22.1
> I0601 23:02:44.662256 14849 sched.cpp:254] New master detected at
> master@127.0.0.1:5050
> I0601 23:02:44.664237 14849 sched.cpp:264] No credentials provided.
> Attempting to register without authentication
> I0601 23:02:44.670964 14853 sched.cpp:448] Framework registered with
> 20150601-225015-16777343-5050-14668-0000
> Registered!
> Received offer 20150601-225015-16777343-5050-14668-O0 with cpus(*):4;
> mem(*):2806; disk(*):40810; ports(*):[31000-32000]
> Launching task 0 using offer 20150601-225015-16777343-5050-14668-O0
> Launching task 1 using offer 20150601-225015-16777343-5050-14668-O0
> Launching task 2 using offer 20150601-225015-16777343-5050-14668-O0
> Launching task 3 using offer 20150601-225015-16777343-5050-14668-O0
> Task 0 is in state TASK_LOST
> Aborting because task 0 is in unexpected state TASK_LOST with reason 1
> from source 1 with message 'Executor terminated'
> I0601 23:02:44.880982 14848 sched.cpp:1623] Asked to abort the driver
> I0601 23:02:44.881239 14848 sched.cpp:856] Aborting framework
> '20150601-225015-16777343-5050-14668-0000'
> I0601 23:02:44.881921 14828 sched.cpp:1589] Asked to stop the driver
>
>
>
> Any help will be appreciated, thanks!
>
>
--
Best Regards,
Haosdent Huang