Currently, when the test is executed too quickly, the timestamp insterted into the 'my_table' table might be the same as the timestamp used in the SELECT statement for comparison. However, the statement only selects rows where the inserted timestamp is strictly lower than current timestamp. As a result, when this comparison fails, we may skip executing the following comparison, which uses a user-defined function, due to which the statement is supposed to fail with an error. Instead, the select statement simply returns no rows and the test case fails. To fix this, simply use the less or equal operator instead of using the strictly less operator for comparing timestamps. Fixes #15616 Closes scylladb/scylladb#15699
68 KiB
68 KiB