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

ASF GitHub Bot commented on STORM-1401:
---------------------------------------

GitHub user d2r opened a pull request:

    https://github.com/apache/storm/pull/966

    [STORM-1401] removes multilang-test

    This test takes over 2 minutes to run, and it does not validate correctness 
of the multilang code.  It basically runs the topologies for a while and passes 
if they do not crash. Since they are now causing repeated failures in automated 
testing, there is not a lot of value in keeping them as-is.
    
    We should cover multilang code as well as the Shell* classes in unit 
testing.  So I will create a follow-on issue to cover these with tests.

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

    $ git pull https://github.com/d2r/storm storm-1401-multilang-test-removal

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

    https://github.com/apache/storm/pull/966.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 #966
    
----
commit 37099d8ee68cd8c440bae34ed2aa0c7f30a4d3c2
Author: Derek Dagit <[email protected]>
Date:   2015-12-22T20:46:37Z

    removes multilang-test

----


> Spurious multilang-test crashes on travis-ci
> --------------------------------------------
>
>                 Key: STORM-1401
>                 URL: https://issues.apache.org/jira/browse/STORM-1401
>             Project: Apache Storm
>          Issue Type: Sub-task
>          Components: storm-multilang
>    Affects Versions: 0.11.0
>            Reporter: Derek Dagit
>            Priority: Minor
>
> One example here: https://travis-ci.org/apache/storm/jobs/97589141#L438
> The test failure does not happen consistently; when they do, they seem to 
> halt the test job.



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

Reply via email to