Comment 4 for bug 1475329

You cannot raise the granularity of timestamp, they go up to the nanosecond. The thing is that the timestamp is provided by the user, and if it provides twice the same timestamp even with the same value, well the problem is going to occur.

I think we should simply ignore the oldest one.

Do you have a unit test case that reproduces this?