Carlos Martín Nieto 863dd89abf tests: tick over five seconds instead of one ... When ticking over one second, it can happen that the actual time ticks over the same second between the time that we undermine our own race protections and the time in which we perform the index update. Such timing would make the time in the entries match the index' timestamp and we have not gained anything. Ticking over five seconds makes it so that if real-time rolls over that second, our index is still ahead. This is still suboptimal as we're dealing with timing, but five seconds should be long enough for any reasonable test runner to finish the tests.		2015-06-20 10:46:10 +02:00
..
binaryunicode.c	Introduce cl_assert_equal_oid	2014-07-01 14:40:16 -04:00
checkout_helpers.c	tests: tick over five seconds instead of one	2015-06-20 10:46:10 +02:00
checkout_helpers.h	tests: tick the index when we count OID calculations	2015-06-16 08:51:45 +02:00
conflict.c	conflict tests: use GIT_IDXENTRY_STAGE_SET	2015-05-28 09:44:22 -04:00
crlf.c	tests: tick the index when we count OID calculations	2015-06-16 08:51:45 +02:00
head.c	git_checkout_opts -> git_checkout_options	2014-03-06 09:44:51 -08:00
icase.c	Fix leaks in tests/checkout/icase	2015-06-12 09:28:47 -07:00
index.c	conflict tests: use GIT_IDXENTRY_STAGE_SET	2015-05-28 09:44:22 -04:00
nasty.c	win32: further cleanups for 8.3 disabling	2015-02-03 20:01:24 -05:00
tree.c	Rename GIT_EMERGECONFLICT to GIT_ECONFLICT	2015-05-29 09:55:09 -04:00
typechange.c	repository: remove log message override for switching the active branch	2015-03-03 14:40:50 +01:00