-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Flaky-test: ReplicatorTest.testReplication #9458
Comments
Similar issues in testReplicatePeekAndSkip method.
Usage tip: To enable automatic navigation to failure message, open the following links with CTRL/CMD-click. Full exception stacktrace
Usage tip: To enable automatic navigation to failure message, open the following links with CTRL/CMD-click. Full exception stacktrace
Usage tip: To enable automatic navigation to failure message, open the following links with CTRL/CMD-click. Full exception stacktrace
|
Flaky-test: org.apache.pulsar.broker.service.ReplicatorTest.testReplication org.apache.pulsar.broker.service.ReplicatorTest is flaky. The testReplication test method fails sporadically.
Usage tip: To enable automatic navigation to failure message, open the following links with CTRL/CMD-click. Full exception stacktrace
Usage tip: To enable automatic navigation to failure message, open the following links with CTRL/CMD-click. Full exception stacktrace
Usage tip: To enable automatic navigation to failure message, open the following links with CTRL/CMD-click. Full exception stacktrace
|
The issue had no activity for 30 days, mark with Stale label. |
Closed as stale. Please create a new issue if it's still relevant to the maintained versions. |
org.apache.pulsar.broker.service.ReplicatorTest is flaky. The testReplication test method fails sporadically.
Usage tip: To enable automatic navigation to failure message, open the following links with CTRL/CMD-click.
example failure 2021-02-01T01:35:59.4539012Z
example failure 2021-02-01T01:35:59.4493873Z
example failure 2021-01-30T07:38:30.7674464Z
example failure 2021-01-30T07:38:30.7639225Z
example failure 2021-01-29T04:50:34.2255253Z
example failure 2021-01-29T04:50:34.2177223Z
example failure 2021-01-29T04:34:55.1330899Z
example failure 2021-01-29T04:34:55.1231886Z
example failure 2021-01-29T00:06:45.0299447Z
example failure 2021-01-29T00:06:45.0264300Z
example failure 2021-01-28T18:15:18.2988053Z
example failure 2021-01-28T18:15:18.2959689Z
example failure 2021-01-26T21:41:26.0735469Z
example failure 2021-01-26T21:41:26.0647243Z
example failure 2021-01-26T02:02:01.4445808Z
example failure 2021-01-26T02:02:01.4403253Z
example failure 2021-01-25T22:27:52.3506097Z
example failure 2021-01-25T22:27:52.3451779Z
example failure 2021-01-25T12:24:27.5671729Z
example failure 2021-01-25T12:24:27.5516331Z
example failure 2021-01-22T11:39:17.6190592Z
example failure 2021-01-22T11:39:17.6113423Z
example failure 2021-01-21T21:09:43.3224477Z
example failure 2021-01-21T21:09:43.3183952Z
Full exception stacktrace
Usage tip: To enable automatic navigation to failure message, open the following links with CTRL/CMD-click.
example failure 2021-02-02T13:46:14.3051150Z
example failure 2021-02-02T13:46:14.2968169Z
example failure 2021-02-01T03:56:01.5185348Z
example failure 2021-02-01T03:56:01.5079380Z
Full exception stacktrace
The text was updated successfully, but these errors were encountered: