You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2013/05/30 00:30:21 UTC
[jira] [Created] (MESOS-487) Balloon framework fails to run due to
bad flags
Vinod Kone created MESOS-487:
--------------------------------
Summary: Balloon framework fails to run due to bad flags
Key: MESOS-487
URL: https://issues.apache.org/jira/browse/MESOS-487
Project: Mesos
Issue Type: Bug
Reporter: Vinod Kone
Assignee: Benjamin Hindman
I suspect this has to do with the latest flags refactor.
[vinod@smfd-bkq-03-sr4 build]$ sudo GLOG_v=1 ./bin/mesos-tests.sh --gtest_filter="*Balloon*" --verbose
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0529 22:28:13.094351 31506 process.cpp:1426] libprocess is initialized on 10.37.184.103:53425 for 24 cpus
I0529 22:28:13.095010 31506 logging.cpp:91] Logging to STDERR
Source directory: /home/vinod/mesos
Build directory: /home/vinod/mesos/build
-------------------------------------------------------------
We cannot run any cgroups tests that require mounting
hierarchies because you have the following hierarchies mounted:
/cgroup
We'll disable the CgroupsNoHierarchyTest test fixture for now.
-------------------------------------------------------------
Note: Google Test filter = *Balloon*-CgroupsNoHierarchyTest.ROOT_CGROUPS_NOHIERARCHY_MountUnmountHierarchy:
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from CgroupsIsolatorTest
[ RUN ] CgroupsIsolatorTest.ROOT_CGROUPS_BalloonFramework
Using temporary directory '/tmp/CgroupsIsolatorTest_ROOT_CGROUPS_BalloonFramework_pWWdE1'
Launched master at 31574
Failed to load unknown flag 'build_dir'
Usage: lt-mesos-master [...]
Supported options:
--allocation_interval=VALUE Amount of time to wait between performing
(batch) allocations (e.g., 500ms, 1sec, etc) (default: 1secs)
--cluster=VALUE Human readable name for the cluster,
displayed in the webui
--framework_sorter=VALUE Policy to use for allocating resources
between a given user's frameworks. Options
are the same as for user_allocator (default: drf)
--[no-]help Prints this help message (default: false)
--ip=VALUE IP address to listen on
--log_dir=VALUE Location to put log files (no default, nothing
is written to disk unless specified;
does not affect logging to stderr)
--logbufsecs=VALUE How many seconds to buffer log messages for (default: 0)
--port=VALUE Port to listen on (default: 5050)
--[no-]quiet Disable logging to stderr (default: false)
--[no-]root_submissions Can root submit frameworks? (default: true)
--slaves=VALUE Initial slaves that should be
considered part of this cluster
(or if using ZooKeeper a URL) (default: *)
--user_sorter=VALUE Policy to use for allocating resources
between users. May be one of:
dominant_resource_fairness (drf) (default: drf)
--webui_dir=VALUE Location of the webui files/assets (default: /usr/local/share/mesos/webui)
--whitelist=VALUE Path to a file with a list of slaves
(one per line) to advertise offers for;
should be of the form: file://path/to/file (default: *)
--zk=VALUE ZooKeeper URL (used for leader election amongst masters)
May be one of:
zk://host1:port1,host2:port2,.../path
zk://username:password@host1:port1,host2:port2,.../path
file://path/to/file (where file contains one of the above) (default: )
{RED}Master crashed; failing test
/home/vinod/mesos/src/tests/balloon_framework_test.sh: line 31: kill: (31574) - No such process
../../src/tests/script.cpp:76: Failure
Failed
balloon_framework_test.sh exited with status 2
[ FAILED ] CgroupsIsolatorTest.ROOT_CGROUPS_BalloonFramework (2031 ms)
[----------] 1 test from CgroupsIsolatorTest (2031 ms total)
[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (2031 ms total)
[ PASSED ] 0 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] CgroupsIsolatorTest.ROOT_CGROUPS_BalloonFramework
1 FAILED TEST
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira