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

Alexander Rojas commented on MESOS-3026:
----------------------------------------

I found a fix for the hang. However I haven't found the reason why the test 
fails in the first place. Most likely it is related to machines configured with 
a locale other than an english based locale (or C locale) which makes 
{{strptime}} fails if the [conversion 
specifications|http://pubs.opengroup.org/onlinepubs/009695399/functions/strptime.html]
  _%a_, _%b_, _%c_, _%p_, _%x_ and _%X_, Which sadly is the case with the [HTTP 
Date|http://tools.ietf.org/html/rfc2616#section-14.29]. This constraint will 
require a custom implementation of a date parsing, as it was done for the [HTTP 
Date 
serialization|https://github.com/apache/mesos/blob/a7de6513cd2ff431a541e93c01858a0330584015/3rdparty/libprocess/src/time.cpp#L23].

I'm stopping process on this ticket given its fall in priority.

*NOTE:* {{strptime}} and {{strftime}} are still safe to use if the conversion 
specifications shown above are not used. That means that current uses of these 
functions are not problems.

> ProcessTest.Cache fails and hangs
> ---------------------------------
>
>                 Key: MESOS-3026
>                 URL: https://issues.apache.org/jira/browse/MESOS-3026
>             Project: Mesos
>          Issue Type: Bug
>          Components: libprocess
>         Environment: ubuntu 15.04/ ubuntu 14.04.2
> clang-3.6 / gcc 4.8.2
>            Reporter: Joris Van Remoortere
>            Assignee: Alexander Rojas
>            Priority: Blocker
>              Labels: libprocess, tests
>
> {code}
> [ RUN      ] ProcessTest.Cache
> ../../../3rdparty/libprocess/src/tests/process_tests.cpp:1726: Failure
> Value of: response.get().status
>   Actual: "200 OK"
> Expected: "304 Not Modified"
> [  FAILED  ] ProcessTest.Cache (1 ms)
> {code}
> The tests then finish running, but the gtest framework fails to terminate and 
> uses 100% CPU.



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

Reply via email to