From ea6c733e45bd6fda609a3f5b1f6519f05b8bcbf2 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 13 Sep 2022 13:19:18 -0400 Subject: [PATCH] comment --- ...ent_1_bd9963c2a40b55bf745ce3d801a5da19._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/some_conflict_resolution_tests_fail_some_time/comment_1_bd9963c2a40b55bf745ce3d801a5da19._comment diff --git a/doc/bugs/some_conflict_resolution_tests_fail_some_time/comment_1_bd9963c2a40b55bf745ce3d801a5da19._comment b/doc/bugs/some_conflict_resolution_tests_fail_some_time/comment_1_bd9963c2a40b55bf745ce3d801a5da19._comment new file mode 100644 index 0000000000..53e6535f91 --- /dev/null +++ b/doc/bugs/some_conflict_resolution_tests_fail_some_time/comment_1_bd9963c2a40b55bf745ce3d801a5da19._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2022-09-13T17:10:07Z" + content=""" +So `git-annex sync` is failing and somehow the failure is silent and all it +prints is "commit". Not "commit ok" or "commit failed" or an error. + +This reminds me of another bug you filed, + +In both cases a git-annex command seems to crash in the middle. + +The other one is also intermittent. Are both running on the same machine? +"""]] -- 2.30.2