[ 
https://issues.apache.org/jira/browse/MESOS-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14963883#comment-14963883
 ] 

Michael Park commented on MESOS-3604:
-------------------------------------

{noformat}
commit bb8409882c1e1b5c7eea2a4528f5d3d33dc639b1
Author: Michael Park <[email protected]>
Date:   Mon Oct 19 12:10:45 2015 -0700

    Fixed `ExamplesTest.PersistentVolumeFramework` on OS X El Capitan.

    The `MESOS_LAUNCHER_DIR` was being set to `<build_dir>/src/.libs`
    rather than `<build_dir>/src`. This leads to us attemping to execute
    `<build_dir>/src/.libs/mesos-executor` which doesn't have the correct
    `DYLD_LIBRARY_PATH` set.

    Review: https://reviews.apache.org/r/39423
{noformat}

> ExamplesTest.PersistentVolumeFramework does not work in OS X El Capitan
> -----------------------------------------------------------------------
>
>                 Key: MESOS-3604
>                 URL: https://issues.apache.org/jira/browse/MESOS-3604
>             Project: Mesos
>          Issue Type: Bug
>          Components: test
>            Reporter: Michael Park
>            Assignee: Michael Park
>              Labels: mesosphere
>             Fix For: 0.26.0
>
>
> The example persistent volume framework test does not pass in OS X El 
> Capitan. It seems to be executing the 
> {{<build_dir>/src/.libs/mesos-executor}} directly while it should be 
> executing the wrapper script at {{<build_dir>/src/mesos-executor}} instead. 
> The no-executor framework passes however, which seem to have a very similar 
> configuration with the persistent volume framework. The following is the 
> output that shows the {{dyld}} load error:
> {noformat}
> I1008 01:22:52.280140 4284416 launcher.cpp:132] Forked child with pid '1706' 
> for contain
> er 'b6d3bd96-2ebd-47b1-a16a-a22ffba992aa'
> I1008 01:22:52.280300 4284416 containerizer.cpp:873] Checkpointing executor's 
> forked pid
>  1706 to 
> '/var/folders/p6/nfxknpz52dzfc6zqnz23tq180000gn/T/mesos-XXXXXX.5OZ3locB/0/meta/
> slaves/34d6329e-69cb-4a72-aee4-fe892bf1c70b-S2/frameworks/34d6329e-69cb-4a72-aee4-fe892b
> f1c70b-0000/executors/dec188d4-d2dc-40c5-ac4d-881adc3d81c0/runs/b6d3bd96-2ebd-47b1-a16a-
> a22ffba992aa/pids/forked.pid'
> dyld: Library not loaded: /usr/local/lib/libmesos-0.26.0.dylib
>   Referenced from: /Users/mpark/Projects/mesos/build/src/.libs/mesos-executor
>   Reason: image not found
> dyld: Library not loaded: /usr/local/lib/libmesos-0.26.0.dylib
>   Referenced from: /Users/mpark/Projects/mesos/build/src/.libs/mesos-executor
>   Reason: image not found
> dyld: Library not loaded: /usr/local/lib/libmesos-0.26.0.dylib
>   Referenced from: /Users/mpark/Projects/mesos/build/src/.libs/mesos-executor
>   Reason: image not found
> I1008 01:22:52.365397 3211264 containerizer.cpp:1284] Executor for container 
> '06b649be-88c8-4047-8fb5-e89bdd096b66' has exited
> I1008 01:22:52.365433 3211264 containerizer.cpp:1097] Destroying container 
> '06b649be-88c8-4047-8fb5-e89bdd096b66'
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to