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

ASF GitHub Bot commented on THRIFT-2919:
----------------------------------------

GitHub user Jens-G opened a pull request:

    https://github.com/apache/thrift/pull/340

    THRIFT-2919 Haxe test server timeout too large

    Client: Haxe
    Patch: Jens Geyer
    
    - reduced timeout and made sure the test script waits appropriately
    - added test to make sure Haxe >= 3.1.3 is used

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Jens-G/thrift thrift-2919

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/thrift/pull/340.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #340
    
----
commit 0bede2fc1266482506c6bd5e75315a06f36ffc56
Author: Jens Geyer <je...@apache.org>
Date:   2014-12-29T18:46:44Z

    THRIFT-2919 Haxe test server timeout too large
    Client: Haxe
    Patch: Jens Geyer
    
    - reduced timeout and made sure the test script waits appropriately
    - added test to make sure Haxe >= 3.1.3 is used

----


> Haxe test server timeout too large
> ----------------------------------
>
>                 Key: THRIFT-2919
>                 URL: https://issues.apache.org/jira/browse/THRIFT-2919
>             Project: Thrift
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 0.9.3
>            Reporter: Jens Geyer
>            Assignee: Jens Geyer
>             Fix For: 0.9.3
>
>
> The timeout used to run the Thrift test server is too high. Because the 
> process lives longer than intended, subsequent tests run by make check may be 
> affected as the are not able to bind() the server socket as long as the 
> previous server runs on the same port.



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

Reply via email to