Don't let timestamps depend on the timer resolution
commitc03d8cba3d23966e6d87b2c9ead76b24a3b8165b
authorAndrey Loskutov <loskutov@gmx.de>
Mon, 30 Mar 2015 17:41:37 +0000 (30 19:41 +0200)
committerAndrey Loskutov <loskutov@gmx.de>
Mon, 30 Mar 2015 17:41:37 +0000 (30 19:41 +0200)
treeb52d109937dc534f1394eaba11c41fe3a3ba22f2
parent08ed70b385cd3665d6b81ba5bf2f22c1d7f0fdce
Don't let timestamps depend on the timer resolution

Looks like on my workstation Java can resolve timestamps up to last
two-three digits, so that file1.getLocalTimeStamp() and
Repository.lastModifiedInIndex() always differ in few hundred
milliseconds.

Reduced timestamps resolution to seconds to avoid unstable tests.

Change-Id: I369353230e0013eab4dd90a661c45398aef134c7
Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
org.eclipse.egit.core.test/src/org/eclipse/egit/core/test/op/AddOperationTest.java