Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[fix][flaky-test]ManagedCursorMetricsTest.testCursorReadWriteMetrics #17045

Merged

Conversation

poorbarcode
Copy link
Contributor

Fixes #16948

Master Issue: #16948

Motivation

This test is flaky because that BK has not been successfully written when the asset executed

metricsList = metrics.generate();
Assert.assertEquals(metricsList.size(), 2);
Assert.assertNotEquals(metricsList.get(0).getMetrics().get("brk_ml_cursor_writeLedgerSize"), 0L);
Assert.assertNotEquals(metricsList.get(0).getMetrics().get("brk_ml_cursor_writeLedgerLogicalSize"), 0L);
Assert.assertEquals(metricsList.get(0).getMetrics().get("brk_ml_cursor_readLedgerSize"), 0L);

Modifications

Makes assert execute after BK written

Documentation

  • doc-required
    (Your PR needs to update docs and you will update later)

  • doc-not-needed
    (Please explain why)

  • doc
    (Your PR contains doc changes)

  • doc-complete
    (Docs have been already added)

@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label Aug 10, 2022
@Technoboy- Technoboy- added this to the 2.11.0 milestone Aug 11, 2022
@codelipenghui codelipenghui added this to Reviewer approved in Apache Pulsar / Flaky Tests Aug 11, 2022
return managedCursor.getStats();
}

@Test(timeOut = 2 * 1000)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can just use the default timeout? Or any reason to set it to 2 seconds for this test? It might become flaky in the CI environment.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or any reason to set it to 2 seconds for this test?

no

We can just use the default timeout?

already change to default timeout.

@poorbarcode
Copy link
Contributor Author

/pulsarbot rerun-failure-checks

2 similar comments
@poorbarcode
Copy link
Contributor Author

/pulsarbot rerun-failure-checks

@poorbarcode
Copy link
Contributor Author

/pulsarbot rerun-failure-checks

@codelipenghui codelipenghui merged commit e0ff3d7 into apache:master Aug 12, 2022
Apache Pulsar / Flaky Tests automation moved this from Reviewer approved to Done Aug 12, 2022
Jason918 pushed a commit that referenced this pull request Sep 4, 2022
nicoloboschi pushed a commit to datastax/pulsar that referenced this pull request Sep 16, 2022
@poorbarcode poorbarcode deleted the flaky/testCursorReadWriteMetrics branch September 17, 2022 02:49
@congbobo184 congbobo184 added the cherry-picked/branch-2.9 Archived: 2.9 is end of life label Nov 11, 2022
congbobo184 pushed a commit that referenced this pull request Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

Flaky-test: ManagedCursorMetricsTest.testCursorReadWriteMetrics
5 participants