From 046a497d7774193c019d53fecc64d0a4b2e7d929 Mon Sep 17 00:00:00 2001
From: Robin Rosenberg <robin.rosenberg@dewire.com>
Date: Tue, 2 Oct 2012 12:45:29 +0200
Subject: [PATCH] Fix unstable test

Add more time to a timestamp to safely go beyond the granularity of
the timestamp resolution of the file system. The lowest resolution we
know of is FAT with two second resolution. Then add some to make sure we
are above the limit.

Change-Id: I85c5b07dcdf2d80de41fe9b2354ccc888bad7f1e
---
 .../tst/org/eclipse/jgit/api/CommitCommandTest.java             | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/org.eclipse.jgit.test/tst/org/eclipse/jgit/api/CommitCommandTest.java b/org.eclipse.jgit.test/tst/org/eclipse/jgit/api/CommitCommandTest.java
index 20d62f531..44f1a48c3 100644
--- a/org.eclipse.jgit.test/tst/org/eclipse/jgit/api/CommitCommandTest.java
+++ b/org.eclipse.jgit.test/tst/org/eclipse/jgit/api/CommitCommandTest.java
@@ -321,7 +321,7 @@ public class CommitCommandTest extends RepositoryTestCase {
 		db.getIndexFile().setLastModified(indexTime - 5000);
 
 		write(file1, "content4");
-		assertTrue(file1.setLastModified(file1.lastModified() + 1000));
+		assertTrue(file1.setLastModified(file1.lastModified() + 2500));
 		assertNotNull(git.commit().setMessage("edit file").setOnly("file1.txt")
 				.call());