gio/tests/g-file-info: don't assume million-in-one events don't happen

The modification time test creates a file, gets the modification time in
seconds, then gets the modification time in microseconds and assumes
that the difference between the two has to be above 0.

As rare as this may be, it can happen:

$ stat g-file-info-test-50A450 -c %y
2021-07-06 18:24:56.000000767 +0100

Change the test to simply assert that the difference not negative to
handle this case.
This commit is contained in:
Ross Burton 2021-07-06 19:26:03 +01:00
parent 0b2f48022b
commit 289f8be1b3

View File

@ -178,7 +178,7 @@ test_g_file_info_modification_time (void)
g_assert_nonnull (dt_usecs); g_assert_nonnull (dt_usecs);
ts = g_date_time_difference (dt_usecs, dt); ts = g_date_time_difference (dt_usecs, dt);
g_assert_cmpint (ts, >, 0); g_assert_cmpint (ts, >=, 0);
g_assert_cmpint (ts, <, G_USEC_PER_SEC); g_assert_cmpint (ts, <, G_USEC_PER_SEC);
/* Try round-tripping the modification time. */ /* Try round-tripping the modification time. */