Flaky testIncDec test about jredistimeseries HOT 4 CLOSED

Yes it seems like there is a timing issue in this test

from jredistimeseries.

@felipecsl
The first time you call ts.incrby you are using the implicit server Unix time. The second time you are using the time from your laptop.
This means your second timestamp might be prior to the first one and you will get an error.
Please note, ts.incrby will update the latest value if it has the same timestamp as the latest sample. If it earlier than the latest, you will get the error message "ts.incrtby...".
I would suggest to remove this test as it might depend on the system on which it is ran.

from jredistimeseries.

you could easily work around that issue by using a current time provider that you could override during tests using a fixed current time. if you don't care about fixing it, then by all means delete the test :)

from jredistimeseries.

you could easily work around that issue by using a current time provider that you could override during tests using a fixed current time. if you don't care about fixing it, then by all means delete the test :)

Agree @felipecsl - given that we want to test incrby and decrby and not the auto-ts feature on this test. The PR #26 addresses this issue.

from jredistimeseries.