Flaky-test: TopicsTest.cleanup

Beschreibung

Error:  Tests run: 43, Failures: 14, Errors: 0, Skipped: 28, Time elapsed: 9.942 s <<< FAILURE! - in org.apache.pulsar.broker.admin.TopicsTest
  Error:  cleanup(org.apache.pulsar.broker.admin.TopicsTest)  Time elapsed: 2.18 s  <<< FAILURE!
  java.lang.ClassCastException: class org.apache.pulsar.broker.namespace.NamespaceService cannot be cast to class org.apache.pulsar.broker.ServiceConfiguration (org.apache.pulsar.broker.namespace.NamespaceService and org.apache.pulsar.broker.ServiceConfiguration are in unnamed module of loader 'app')
  	at org.apache.pulsar.broker.PulsarService.getConfiguration(PulsarService.java:620)
  	at org.apache.pulsar.broker.auth.MockedPulsarServiceBaseTest.stopBroker(MockedPulsarServiceBaseTest.java:299)
  	at org.apache.pulsar.broker.auth.MockedPulsarServiceBaseTest.internalCleanup(MockedPulsarServiceBaseTest.java:239)

Contributor Guide

Tech Stack

java

Domain

backendtesting

Issue Type

bug

SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.

3

Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.

half day

AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.

stale

KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.

clear

Voraussetzungen

Java programmingJUnit testingApache Pulsar basicsMocking concepts

EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.

45

Research-Richtung

Investigate the flaky test TopicsTest.cleanup by examining the test file TopicsTest.java and the base class MockedPulsarServiceBaseTest. Focus on the stack trace showing a ClassCastException in PulsarService.getConfiguration. The issue suggests a mismatch between the expected type in the test setup. Look at the method stopBroker and internalCleanup to see where the wrong object is being cast. Also check if there are any recent commits that might have introduced this issue. Consider adding more robust mocking or ensuring that the PulsarService is configured with the correct ServiceConfiguration instance.