[ 
https://issues.apache.org/jira/browse/THRIFT-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James E. King, III updated THRIFT-4106:
---------------------------------------
    Description: 
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...)

Travis CI builds are also showing an occasional failure in the test.

  was: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...)


> concurrency_test fails randomly
> -------------------------------
>
>                 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), travis CI
>            Reporter: James E. King, III
>            Assignee: James E. King, III
>            Priority: Critical
>
> 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...)
> Travis CI builds are also showing an occasional failure in the test.



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

Reply via email to