[
https://issues.apache.org/jira/browse/MESOS-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564574#comment-13564574
]
Benjamin Mahler commented on MESOS-341:
---------------------------------------
Looks like for these to work, you have to either:
1. Set the variables inside bin/mesos-build.env.sh prior to running the test
binary, or
2. Install mesos on the machine
I think these used to always work for me simply because we used to always use
"libmesos-0.9.0" which happened to be installed on my test machine, whereas now
we use "libmesos-0.12.0".
Do we want these binaries to perform (1) prior to running?
> Regression in running example frameworks.
> -----------------------------------------
>
> Key: MESOS-341
> URL: https://issues.apache.org/jira/browse/MESOS-341
> Project: Mesos
> Issue Type: Bug
> Reporter: Benjamin Mahler
>
> Getting the following error from the slave:
> Fetching resources into
> /tmp/mesos/slaves/201301280515-2081170186-51464-58350-0/frameworks/201301280515-2081170186-51464-58350-0000/executors/default/runs/5b43821a-eb30-4af4-8614-09eede507d94
> /home/bmahler/git/mesos/build/src/.libs/balloon-executor: error while loading
> shared libraries: libmesos-0.12.0.so: cannot open shared object file: No such
> file or directory
> I0128 05:15:56.537960 58364 process_based_isolation_module.cpp:277] Telling
> slave of lost executor default of framework
> 201301280515-2081170186-51464-58350-0000
> But looking at the .libs:
> [build] $ ls src/.libs/libmesos-0.12.0.so
> .libs/libmesos-0.12.0.so
--
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
