flume-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLUME-2997) Fix flaky junit test in SpillableMemoryChannel
Date Thu, 27 Oct 2016 12:10:58 GMT

    [ https://issues.apache.org/jira/browse/FLUME-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15611692#comment-15611692

Hudson commented on FLUME-2997:

FAILURE: Integrated in Jenkins build Flume-trunk-hbase-1 #222 (See [https://builds.apache.org/job/Flume-trunk-hbase-1/222/])
FLUME-2997. Fix flaky test in SpillableMemoryChannel (bessbd: [http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=7c4b2fd3e88f038dea3bdae01eb864547770ad48])
* (edit) flume-ng-channels/flume-spillable-memory-channel/src/test/java/org/apache/flume/channel/TestSpillableMemoryChannel.java

> Fix flaky junit test in SpillableMemoryChannel
> ----------------------------------------------
>                 Key: FLUME-2997
>                 URL: https://issues.apache.org/jira/browse/FLUME-2997
>             Project: Flume
>          Issue Type: Test
>    Affects Versions: v1.7.0
>            Reporter: Attila Simon
>            Assignee: Attila Simon
>             Fix For: v1.8.0
>         Attachments: FLUME-2997-1.patch, FLUME-2997.patch
> testParallelSingleSourceAndSink sometimes trigger an edge case scenario if sinks are
slower than sources. In such situations the channel can get full thus uncaught ChannelFullException
breaks the test. Since testCapacityWithOverflow was designed to cover such edge-case scenario
already we can safely fix the test by increasing the channel capacity to make sure it won't
get full.

This message was sent by Atlassian JIRA

View raw message