[jira] [Comment Edited] (MESOS-798) ExamplesTest.PythonFramework failing

["Till Toenshoff (JIRA)" <ji...@apache.org>]

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

Till Toenshoff edited comment on MESOS-798 at 12/20/13 6:11 AM:
----------------------------------------------------------------

The autoconf check does have to be rather complex for covering the issue (possibly this and definitely MESOS-799). It would need to build and test-run a minimal egg that links against a static library that imports a standard C(++) library object.
A static library (built using the standard mesos build settings) is needed in this puzzle because the egg producing distutils possibly use slightly different build settings (derived from python-config). 
If that check succeeds, we can be rather sure that the mesos-egg itself will be functional from a build-env point of view.

Are we ok with such test during the autoconf phase?


was (Author: tillt):
The autoconf check does have to be rather complex for covering the issue (possibly this and definitely MESOS-799). It would need to build and test-run a minimal egg that links against a static library that imports a standard C(++) library object.
A static library (built using the standard mesos build settings) is needed in this puzzle because the egg producing distutils possibly use slightly different build settings (derived from python-config). 
If that check succeeds, we can by rather sure that the mesos-egg itself will be functional.

Are we ok with such test during the autoconf phase?

> ExamplesTest.PythonFramework failing 
> -------------------------------------
>
>                 Key: MESOS-798
>                 URL: https://issues.apache.org/jira/browse/MESOS-798
>             Project: Mesos
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.16.0
>         Environment: Linux 2.6.32-279.el6.x86_64
> Python 2.6.6
> Python Packages installed
> python-2.6.6-37.el6_4.x86_64
> protobuf-python-2.3.0-7.el6.x86_64
> python-libs-2.6.6-37.el6_4.x86_64
> python-devel-2.6.6-37.el6_4.x86_64
> python-setuptools-0.6.10-3.el6.noarch
> python-boto-2.13.3-1.el6.noarch
>            Reporter: Bernardo Gomez Palacio
>              Labels: test
>
> (Based on Git Commit Hash 03b9407)
> Running `make check` fails while executing ExamplesTest.PythonFramework with the following trace:
> [ RUN      ] ExamplesTest.PythonFramework
> Using temporary directory '/tmp/ExamplesTest_PythonFramework_5Vv4TM'
> Traceback (most recent call last):
>   File "/builddir/build/BUILD/mesos-03b94076caddceda4c0a6a03aa44ebe4d64f1acc/src/examples/python/test_framework.py", line 23, in <module>
>     import mesos
>   File "build/bdist.linux-x86_64/egg/mesos.py", line 26, in <module>
>   File "build/bdist.linux-x86_64/egg/_mesos.py", line 7, in <module>
>   File "build/bdist.linux-x86_64/egg/_mesos.py", line 6, in __bootstrap__
>   File "build/bdist.linux-x86_64/egg/mesos_pb2.py", line 1545, in <module>
> AttributeError: 'FileDescriptor' object has no attribute 'message_types_by_name'
> tests/script.cpp:77: Failure
> Failed
> python_framework_test.sh exited with status 1
> [  FAILED  ] ExamplesTest.PythonFramework (432 ms)
> [----------] 5 tests from ExamplesTest (4346 ms total)



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)