Flaky-test: TopicsTest.cleanup

Description

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

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

half day

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

Java programmingJUnit testingApache Pulsar basicsMocking concepts

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

45

Research direction

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.