From 9e1a797fb7795f3ac6d6a41617b0da571a655235 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 25 Jan 2021 12:31:47 -0400 Subject: [PATCH] comment --- ...nt_2_1fb916ff03e0b8c96c554caf1558ecab._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/bugs/export__95__import_fails_on_crippled_FS_on_ubuntu/comment_2_1fb916ff03e0b8c96c554caf1558ecab._comment diff --git a/doc/bugs/export__95__import_fails_on_crippled_FS_on_ubuntu/comment_2_1fb916ff03e0b8c96c554caf1558ecab._comment b/doc/bugs/export__95__import_fails_on_crippled_FS_on_ubuntu/comment_2_1fb916ff03e0b8c96c554caf1558ecab._comment new file mode 100644 index 0000000000..76752cee51 --- /dev/null +++ b/doc/bugs/export__95__import_fails_on_crippled_FS_on_ubuntu/comment_2_1fb916ff03e0b8c96c554caf1558ecab._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2021-01-25T16:28:17Z" + content=""" +Confirmed that a sleep at the right place in the test suite avoids the +failure. Unsure yet why the test suite's existing mtime managing didn't manage +to. + +I do think this should be fixed in the test suite; it's acceptable +that, if using a FS like FAT that doesn't support high-rest mtimes, +git-annex not deal with high-frequency modifications. The same behavior +could already have happened on FAT when it was including the inode, +if the modifications were done w/o overwriting changing the inode. +"""]] -- 2.30.2