The reason for the flakiness of this test is due to non-deterministic order of the measurements returned by the function statement.getMeasurements(). Fixed the issue by comparing the measurements as Set instead of List as Set ensures a deterministic order.
Please let me know if you have any questions or need any additional justification/changes from my side.
This PR has:
[ ] been self-reviewed.
[ ] concurrent read
[ ] concurrent write
[ ] concurrent read and write
[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods.
[ ] added or updated version, license, or notice information
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious
for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold
for code coverage.
[ ] added integration tests.
[ ] been tested in a test IoTDB cluster.
Key changed/added classes (or packages if there are too many classes) in this PR
Description
This PR fixes the non deterministic test :
This tests failed under NonDex tool as explained in the issue IOTDB-6352 .
Steps to Reproduce
To reproduce the problem, first build the module and then run the nondex command:
The reason for the flakiness of this test is due to non-deterministic order of the measurements returned by the function statement.getMeasurements(). Fixed the issue by comparing the measurements as Set instead of List as Set ensures a deterministic order.
Please let me know if you have any questions or need any additional justification/changes from my side.
This PR has:
Key changed/added classes (or packages if there are too many classes) in this PR