From 8ba2109395768f7292523d2d4bccfec658206894 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Thu, 23 May 2019 17:07:40 +0000 Subject: [PATCH] Added a comment --- ...omment_2_96312bab546412b1eecfa74aec1d7fee._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/bugs/still_seeing_errors_with_parallel_git-annex-add/comment_2_96312bab546412b1eecfa74aec1d7fee._comment diff --git a/doc/bugs/still_seeing_errors_with_parallel_git-annex-add/comment_2_96312bab546412b1eecfa74aec1d7fee._comment b/doc/bugs/still_seeing_errors_with_parallel_git-annex-add/comment_2_96312bab546412b1eecfa74aec1d7fee._comment new file mode 100644 index 0000000000..14598c58c3 --- /dev/null +++ b/doc/bugs/still_seeing_errors_with_parallel_git-annex-add/comment_2_96312bab546412b1eecfa74aec1d7fee._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="comment 2" + date="2019-05-23T17:07:40Z" + content=""" +I'll try to reproduce this and re-run under `strace`. Maybe also, take another look at [[todo/add_tests_under_concurrency]]? I think that re-running concurrent operations on a small repo many times should test all relevant operation interleavings, and bring out the concurrency-specific bugs. + +With large repos, concurrency is the only way to make operations run in sane time. So fixing this would help a lot. + +"""]]