diff options
| author | Nick Mathewson <nickm@torproject.org> | 2016-01-29 09:18:59 -0500 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2016-01-29 09:18:59 -0500 |
| commit | 5f7df92571ec5a2d1eddb257e22f5489acc4fc83 (patch) | |
| tree | 9ef43ebc29ec04a5fe42f2411b3aa61ac2f643c8 /src/test/test_dir.c | |
| parent | a5bed4dab2f8521f744d5137e4f439b073c7e5e9 (diff) | |
| download | tor-5f7df92571ec5a2d1eddb257e22f5489acc4fc83.tar.gz tor-5f7df92571ec5a2d1eddb257e22f5489acc4fc83.zip | |
Remove support for unsigned time_t
We've never actually tested this support, and we should probably assume
it's broken.
To the best of my knowledge, only OpenVMS has this, and even on
OpenVMS it's a compile-time option to disable it. And I don't think
we build on openvms anyway. (Everybody else seems to be working
around the 2038 problem by using a 64-bit time_t, which won't expire
for roughly 292 billion years.)
Closes ticket 18184.
Diffstat (limited to 'src/test/test_dir.c')
| -rw-r--r-- | src/test/test_dir.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/src/test/test_dir.c b/src/test/test_dir.c index 4824a94132..83a8b8ccc6 100644 --- a/src/test/test_dir.c +++ b/src/test/test_dir.c @@ -3312,7 +3312,6 @@ test_dir_download_status_schedule(void *arg) tt_assert(increment == expected_increment); tt_assert(dls_failure.next_attempt_at == TIME_MIN + expected_increment); -#if TIME_T_IS_SIGNED delay1 = INT_MAX; increment = download_status_schedule_get_delay(&dls_failure, schedule, @@ -3320,7 +3319,6 @@ test_dir_download_status_schedule(void *arg) expected_increment = delay1; tt_assert(increment == expected_increment); tt_assert(dls_failure.next_attempt_at == TIME_MAX); -#endif delay1 = 0; increment = download_status_schedule_get_delay(&dls_attempt, |