| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | tests: tick over five seconds instead of one | Carlos Martín Nieto | 2015-06-20 | 1 | -1/+1 |
| | | | | | | | | | | | | | | 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. | ||||
| * | Fixed Xcode 6.1 build warnings | Pierre-Olivier Latour | 2015-06-17 | 1 | -1/+0 |
| | | |||||
| * | Introduce p_utimes and p_futimes | Edward Thomson | 2015-06-16 | 1 | -5/+7 |
| | | | | | | | Provide functionality to set the time on a filesystem entry, using utimes or futimes on POSIX type systems or SetFileTime on Win32. | ||||
| * | tests: tick the index when we count OID calculations | Carlos Martín Nieto | 2015-06-16 | 1 | -0/+20 |
| | | | | | | | | | | These tests want to test that we don't recalculate entries which match the index already. This is however something we force when truncating racily-clean entries. Tick the index forward as we know that we don't perform the modifications which the racily-clean code is trying to avoid. | ||||
| * | Rename tests-clar to tests | Ben Straub | 2013-11-14 | 1 | -0/+130 |
 |
index : delta/libgit2.git | |
| github.com: libgit2/libgit2.git |
| summaryrefslogtreecommitdiff |