[fix][broker] Fix seeking by timestamp can be reset the cursor position to earliest #15915
dao-junpulsar-ci-flaky.yaml
on: pull_request
Preconditions
8s
Flaky tests suite
29m 4s
Annotations
2 errors and 2 warnings
|
Flaky tests suite
Process completed with exit code 1.
|
|
TopicReaderTest.testMultiReaderIsAbleToSeekWithTimeOnBeginningOfTopic:
pulsar-broker/src/test/java/org/apache/pulsar/client/api/TopicReaderTest.java#L1278
java.util.concurrent.ExecutionException: org.apache.pulsar.client.api.PulsarClientException: Failed to seek the subscription multiTopicsReader-ded2ce8a2d of the topic persistent://my-property/my-ns/MultiReaderSeekWithTimeOnBeginningOfTopic-partition-1 to the timestamp -60
{"errorMsg":"Reset subscription to publish time error: org.apache.bookkeeper.mledger.ManagedLedgerException: No entries available","reqId":4449808258356420621, "remote":"localhost/127.0.0.1:40341", "local":"/127.0.0.1:59100"}
|
|
Flaky tests suite
Summary: Tests in class org.apache.pulsar.client.api.ClientDeduplicationFailureTest created 73 new threads. There are now 82 threads in total.
|
|
Flaky tests suite
Summary: Tests in class org.apache.pulsar.broker.service.RackAwareTest created 5 new threads. There are now 85 threads in total.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
Unit-BROKER_FLAKY-dumps
|
17.4 KB |
|
|
Unit-BROKER_FLAKY-surefire-reports
|
32.2 MB |
|