Skip to content

Intermittent test fail on BatchMessageTest.testSimpleBatchProducerConsumer #13

Description

@merlimat

Output from Travis build:

com.yahoo.pulsar.client.admin.internal.BrokerStatsImpl$$EnhancerByMockitoWithCGLIB$$fb883741@6b353df8
Tests run: 361, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 831.053 sec <<< FAILURE! - in TestSuite
testSimpleBatchProducerConsumer(com.yahoo.pulsar.broker.service.BatchMessageTest)  Time elapsed: 0.306 sec  <<< FAILURE!
java.lang.AssertionError: expected [0] but found [4]
    at com.yahoo.pulsar.broker.service.BatchMessageTest.testSimpleBatchProducerConsumer(BatchMessageTest.java:293)

Activity

  1. added this to the 1.15 milestone on Sep 13, 2016
  2. radekg commented on Sep 24, 2016

    @radekg
    Contributor

    FYI: I have not experienced this while working on #26

  3. radekg commented on Sep 27, 2016

    @radekg
    Contributor

    @merlimat I just tried the following pr https://github.com/radekg/pulsar/pull/5/files on this test, modified, changed the invocationCount

        @Test(invocationCount = 1000)
        public void testNonBatchCumulativeAckAfterBatchPublish() throws Exception {
          ...

    and I do not have any failures locally. However, looking at the failure in another random place on the linked PR (direct travis URI: https://travis-ci.org/radekg/pulsar/builds/163260260), I think the intermittent errors are caused by using sync tests on an async code.

  4. radekg commented on Sep 28, 2016

    @radekg
    Contributor

    The next commit passes: https://travis-ci.org/radekg/pulsar/builds/163267361. Slightest blip on the main thread and some tests collapse.

  5. modified the milestones: 1.15, 1.16 on Oct 17, 2016
  6. modified the milestones: 1.16, 1.17 on Jan 23, 2017
  7. removed this from the 1.17 milestone on Feb 23, 2017
  8. merlimat commented on Feb 23, 2017

    @merlimat
    ContributorAuthor

    Didn't see this failure in long time, closing for now

  9. added a commit that references this issue on Sep 10, 2019
  10. added a commit that references this issue on May 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions