Hi,
On Fri, May 13, 2016 at 9:28 AM Angela Schreiber wrote:
> On 13/05/16 15:13, "Julian Reschke" wrote:
> >Maybe there's code missing ensuring that System.currentTimeMillis()
> >actually changed before doing the operation that's suppose to lead to a
> >new timestamp?
>
> that might well be. i
hi julian
On 13/05/16 15:13, "Julian Reschke" wrote:
>...with this change,
change? hasn't the test just been introduced with that commit?
*confused*
>testSyncExternalUsersLastSyncedProperty fails
>reliably on my machines, because the two timestamps are the same.
ok...
>
>Maybe there's code
...with this change, testSyncExternalUsersLastSyncedProperty fails
reliably on my machines, because the two timestamps are the same.
Maybe there's code missing ensuring that System.currentTimeMillis()
actually changed before doing the operation that's suppose to lead to a
new timestamp?
Best
