You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[test] TableManagerITCase.testMetadataWithPartition fails on macOS arm64 #3619
I searched in the issues and found nothing similar.
Fluss version
main (development)
Please describe the bug 🐞
TableManagerITCase.testMetadataWithPartition fails consistently for me when run locally on macOS arm64 against main.
The failure happens in the second parameterized invocation, corresponding to isCoordinatorServer=false, while waiting for partition bucket LeaderAndIsr metadata in ZooKeeper:
TableManagerITCase.testMetadataWithPartition:600
Expecting Optional to contain a value but it was empty.
at org.apache.fluss.server.testutils.FlussClusterExtension.waitUntilAllReplicaReady(...)
I also tested a clean local main checkout/export and reproduced the same failure there, so this does not appear related to my feature branch.
The same targeted test passes when run inside a Linux Docker container using maven:3.9.9-eclipse-temurin-11, so this looks like a macOS arm64-specific local test/environment issue.
The README lists Mac OS X as a supported Unix-like build environment, so this may be worth tracking even if CI/self-hosted Linux passes.
Solution
No confirmed fix yet.
A useful first step would be to determine whether TableManagerITCase.testMetadataWithPartition is expected to pass on macOS arm64. If Linux is the intended validation environment for server integration tests, the project could document that more explicitly or provide a lightweight Docker-based Maven test helper for contributors.
Potentially just a local environment issue. But worth tracking in case encountered by anyone else, and might be a good chance to clarify local test environment in documentation
Activity
JandyTenedora commentedon Jul 8, 2026
Potentially just a local environment issue. But worth tracking in case encountered by anyone else, and might be a good chance to clarify local test environment in documentation