Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
Code
-
Low
-
Low Hanging Fruit
-
Unit Test
-
All
-
None
-
Description
I don't know if it was reported but we can see it fail sometimes.
The reason is that it checks the metrics before issuing and query and after. It expects that the executed operation between subsequent metrics checks is the only operation during that time. However the driver sometimes may refresh the schema in the middle and pollute the results. It is perfectly enough to slow down the execution a bit and the test starts to fail consistently rather than sporadically because we always hit schema refresh.