You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "José Guilherme Vanz (JIRA)" <ji...@apache.org> on 2015/08/14 05:32:46 UTC
[jira] [Comment Edited] (MESOS-3189) TimeTest.Now fails with
--enable-libevent
[ https://issues.apache.org/jira/browse/MESOS-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696377#comment-14696377 ]
José Guilherme Vanz edited comment on MESOS-3189 at 8/14/15 3:32 AM:
---------------------------------------------------------------------
I was trying simulate this issue, but I could not.
I executed `configure --enable-libevent` and `make check` in the current HEAD commit and the `TimeTest.Now(0ms)` test is passing.
I'm using Fedora 22, maybe are there some issue in the libevent in other OS? What is your environment?
was (Author: jvanz):
I'm trying simulate these problem, but I could not.
I executed `configure --enable-libevent` and `make check` in the current HEAD commit and the `TimeTest.Now(0ms)` test is passing.
I'm using Fedora 22, maybe are there some issue in the libevent in other OS? What is your environment?
> TimeTest.Now fails with --enable-libevent
> -----------------------------------------
>
> Key: MESOS-3189
> URL: https://issues.apache.org/jira/browse/MESOS-3189
> Project: Mesos
> Issue Type: Bug
> Components: libprocess
> Affects Versions: 0.23.0
> Reporter: Joris Van Remoortere
> Labels: beginner, libprocess, mesosphere, newbie
>
> [ RUN ] TimeTest.Now
> ../../../3rdparty/libprocess/src/tests/time_tests.cpp:50: Failure
> Expected: (Microseconds(10)) < (Clock::now() - t1), actual: 8-byte object <10-27 00-00 00-00 00-00> vs 0ns
> [ FAILED ] TimeTest.Now (0 ms)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)