Skip to content
Pulsar CI Flaky

[fix][broker] PIP-379 Key_Shared implementation racecondition causing out-of-order message delivery #15783

Sign in to view logs

[fix][broker] PIP-379 Key_Shared implementation racecondition causing out-of-order message delivery

[fix][broker] PIP-379 Key_Shared implementation racecondition causing out-of-order message delivery #15783

Triggered via pull request January 21, 2025 17:39
@lhotarilhotari
synchronize #23874
lhotari:lh-key_shared-ordering-racecondition-fix
Status Success
Total duration 32m 37s
Artifacts 2

pulsar-ci-flaky.yaml

on: pull_request
Preconditions
12s
Preconditions
Flaky tests suite
32m 11s
Flaky tests suite
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
PersistentDispatcherFailoverConsumerTest.testAddRemoveConsumer: pulsar-broker/src/test/java/org/apache/pulsar/broker/service/PersistentDispatcherFailoverConsumerTest.java#L383
expected object to not be null
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 3 new threads. There are now 83 threads in total.
Flaky tests suite
Summary: Tests in class org.apache.pulsar.broker.service.PersistentDispatcherFailoverConsumerTest created 2 new threads. There are now 83 threads in total.
Flaky tests suite
Summary: Tests in class org.apache.pulsar.broker.loadbalance.extensions.ExtensibleLoadManagerImplTest created 7 new threads. There are now 16 threads in total.

Artifacts

Produced during runtime
Name Size
Jacoco-coverage-report-flaky
14.8 MB
Unit-BROKER_FLAKY-dumps
31 KB