This message was deleted.

It runs in the Github actions on the master branch periodically, and also on every PR (which should be green before merging the PR) Latest run: https://github.com/apache/druid/actions/runs/6888385335/job/18739047765

Thanks for the link @Laksh Singla . If you look at my surefire reports, failing tests are from druid-processing module. Infact the logs from https://github.com/apache/druid/actions/runs/6888385335/job/18739047765 which says standard-its doesn't test druid-processing module. I found something else under here, unit tests (jdk17, sql-compat=true) • processing modules test https://github.com/apache/druid/actions/runs/6888385335/job/18739042455#step:11:21 Seems like this is testing druid-processing. Wow Test build is GREEN. I wonder why its failing for me? 1. Is there any specific parameters passed along with mvn command in the CI which initialises the NullHandling? Or 2. NullHandling is initialised by another Test class in its static block before it hits the Test class which is failing for me? Another thing is the order of test class execution. When we look at here https://github.com/apache/druid/actions/runs/6888385335/job/18739042455#step:11:152 The Test starts with org.apache.druid.timeline package and the first Test class is VersionedIntervalTimelineSpecificDataTest On my Dev box, test starts with org.apache.druid.query package and the error is from the first test class itself SchemaEvolutionTest [INFO] Running org.apache.druid.query.SchemaEvolutionTest [ERROR] Tests run: 6, Failures: 0, Errors: 6, Skipped: 0, Time elapsed: 0.278 s <<< FAILURE! -- in org.apache.druid.query.SchemaEvolutionTest [ERROR] org.apache.druid.query.SchemaEvolutionTest.testNumericEvolutionTimeseriesAggregation(true) [0] -- Time elapsed: 0.074 s <<< ERROR! java.lang.NoClassDefFoundError: Could not initialize class org.apache.druid.query.QueryRunnerTestHelper Caused by: java.lang.ExceptionInInitializerError: Exception java.lang.IllegalStateException: NullHandling module not initialized, call NullHandling.initializeForTests() [in thread "main"] Kindly correct me if am missing anything.

I am not sure why this is not failing in the pipeline then, perhaps running the tests all at once causes them to pass (?). Can you try out one thing, for the test classes failing with the

Exception java.lang.IllegalStateException: NullHandling module not initialized, call NullHandling.initializeForTests

can you try adding the extends statement like

public class FailingTest extends InitializedNullHandlingTest

and see if it passes. I think it should then.

Can you confirm that the reported Test classes are indeed generating ERRORs on execution on any of the developer machines?

Can confirm this is not passing in my local machine as well. Then it’s an issue with how surefire is running the tests.