You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "James E. King, III (JIRA)" <ji...@apache.org> on 2017/08/12 23:26:00 UTC

[jira] [Commented] (THRIFT-4106) concurrency_test fails randomly on MinGW

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

James E. King, III commented on THRIFT-4106:
--------------------------------------------

It also seems to fail on WIN32 x86 (32-bit) builds, which is why it is disabled in appveyor.yml.

> concurrency_test fails randomly on MinGW
> ----------------------------------------
>
>                 Key: THRIFT-4106
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4106
>             Project: Thrift
>          Issue Type: Bug
>          Components: C++ - Library
>    Affects Versions: 0.10.0
>         Environment: MinGW (appveyor)
>            Reporter: James E. King, III
>            Assignee: James E. King, III
>
> While adding Appveyor build support for MinGW (THRIFT-4081), this test failed periodically.  It would throw an exception in ThreadFactoryTest reapTest where it calls monitor.wait(1000).  It is reproducible locally as well if you have msys2/mingw64 and can use the instructions in the msys2 readme in build/cmake.  The test has been disabled in mingw appveyor builds for now (those builds are new...)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)