Start by ensuring the /tmp/milvus directory is completely cleared before running the tests using the command rm -rf /tmp/milvus. Update the configs/milvus.yaml file to replace all instances of /var/lib/milvus with /tmp/milvus, ensuring consistent management of temporary files during testing. Then, reinitialize the Docker development environment by navigating to the deployments/docker/dev directory, removing existing volume data using sudo rm -rf ./volumes, and restarting the Docker environment with docker compose up -d. After completing these steps, return to the project’s root directory and run the tests using make test-go. If you want to isolate the issue further, you can run specific tests individually with the command go test -v "./internal/util/bloomfilter..." -failfast -test.run TestPerformance_MultiBF. I think these steps should help resolve the RocksDB-related conflicts and allow the unit tests to run successfully.