Skip to content
Pulsar CI Flaky

[fix][broker] Geo Replication lost messages or frequently fails due to Deduplication is not appropriate for Geo-Replication #15853

Sign in to view logs

[fix][broker] Geo Replication lost messages or frequently fails due to Deduplication is not appropriate for Geo-Replication

[fix][broker] Geo Replication lost messages or frequently fails due to Deduplication is not appropriate for Geo-Replication #15853

Triggered via pull request January 27, 2025 01:50
@poorbarcodepoorbarcode
synchronize #23697
poorbarcode:fix/repl_sequence_id
Status Failure
Total duration 29m 5s
Artifacts 2

pulsar-ci-flaky.yaml

on: pull_request
Preconditions
10s
Preconditions
Flaky tests suite
28m 43s
Flaky tests suite
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
Flaky tests suite
Process completed with exit code 1.
RGUsageMTAggrWaitForAllMsgsTest.testMTProduceConsumeRGUsagePersistentTopicNamesDifferentTenant: pulsar-broker/src/test/java/org/apache/pulsar/broker/resourcegroup/RGUsageMTAggrWaitForAllMsgsTest.java#L103
expected [400] but found [0]
RGUsageMTAggrWaitForAllMsgsTest.testMTProduceConsumeRGUsagePersistentTopicNamesSameTenant: pulsar-broker/src/test/java/org/apache/pulsar/broker/resourcegroup/RGUsageMTAggrWaitForAllMsgsTest.java#L98
expected [400] but found [0]
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 Expired
17.4 KB
Unit-BROKER_FLAKY-surefire-reports Expired
32 MB