[jira] [Comment Edited] (KAFKA-8011) Flaky Test RegexSourceIntegrationTest#testRegexMatchesTopicsAWhenCreated

["Bill Bejeck (JIRA)" <ji...@apache.org>]

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

Bill Bejeck edited comment on KAFKA-8011 at 3/1/19 3:09 PM:
------------------------------------------------------------

I've been able to verify that both 1.0 and 1.1 tests pass locally.  If there is a failure in a subsequent build should I revert the cherry-pick?

 

EDIT: Additionally the error message

 
{noformat}
Exception in thread "regex-source-integration-test-e94954f0-2bda-4967-89ee-3de8a64522ea-StreamThread-6" org.apache.kafka.streams.errors.TopologyException: Invalid topology: Topic foo is already matched for another regex pattern foo.* and hence cannot be matched to this regex pattern f.* any more.{noformat}
includes a topic name that is not even in the test.

 

The commit only changed the type of the List used in two tests; I made no logic changes were at all.


was (Author: bbejeck):
I've been able to verify that both 1.0 and 1.1 tests pass locally.  If there is a failure in a subsequent build should I revert the cherry-pick?

> Flaky Test RegexSourceIntegrationTest#testRegexMatchesTopicsAWhenCreated
> ------------------------------------------------------------------------
>
>                 Key: KAFKA-8011
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8011
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>            Reporter: Bill Bejeck
>            Assignee: Bill Bejeck
>            Priority: Critical
>              Labels: flaky-test, newbie
>         Attachments: streams_1_0_test_results.png, streams_1_1_tests.png
>
>
> The RegexSourceIntegrationTest#testRegexMatchesTopicsAWhenCreated
> and RegexSourceIntegrationTest#testRegexMatchesTopicsAWhenDeleted  tests use an ArrayList to assert the topics assigned to the Streams application. 
> The ConsumerRebalanceListener used in the test operates on this list as does the TestUtils.waitForCondition() to verify the expected topic assignments.
> Using the same list in both places can cause a ConcurrentModficationException if the rebalance listener modifies the assignment at the same time TestUtils.waitForCondition() is using the list to verify the expected topics. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)