mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florian Leibert (flo) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-288) Latest trunk does not finish make check
Date Tue, 09 Oct 2012 19:24:02 GMT

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

Florian Leibert (flo) commented on MESOS-288:
---------------------------------------------

root@i-f090d68d:/srv/mesos/src/build# g++ --version
g++ (Ubuntu/Linaro 4.6.1-9ubuntu3) 4.6.1
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


                
> Latest trunk does not finish make check
> ---------------------------------------
>
>                 Key: MESOS-288
>                 URL: https://issues.apache.org/jira/browse/MESOS-288
>             Project: Mesos
>          Issue Type: Bug
>         Environment: Ubuntu 12.04 
>            Reporter: Florian Leibert (flo)
>            Assignee: Vinod Kone
>            Priority: Blocker
>
> make check yields the following error:
> srv/mesos/src/src/tests/stout_tests.cpp: In member function ‘virtual void StoutUtilsTest_rmdir_Test::TestBody()’:
> /srv/mesos/src/src/tests/stout_tests.cpp:316:30: error: uninitialized const ‘EMPTY’
[-fpermissive]
> /srv/mesos/src/third_party/libprocess/include/stout/hashset.hpp:17:7: note: ‘const
class hashset<std::basic_string<char> >’ has no user-provided default constructor
> ...
> make[3]: Leaving directory `/srv/mesos/src/build/src'
> make[2]: *** [check-am] Error 2
> make[2]: Leaving directory `/srv/mesos/src/build/src'
> make[1]: *** [check] Error 2
> make[1]: Leaving directory `/srv/mesos/src/build/src'
> make: *** [check-recursive] Error 1

--
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

Mime
View raw message