From 9109e154c9fbd0eeee5b09d1769dd824817f4f63 Mon Sep 17 00:00:00 2001 From: jkniiv Date: Tue, 24 May 2022 02:46:17 +0000 Subject: [PATCH] Added a comment --- ...t_1_e043a71b60999cf97bd872d8b32fcac9._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/tasty_test_limiting_broken_by_concurrency/comment_1_e043a71b60999cf97bd872d8b32fcac9._comment diff --git a/doc/bugs/tasty_test_limiting_broken_by_concurrency/comment_1_e043a71b60999cf97bd872d8b32fcac9._comment b/doc/bugs/tasty_test_limiting_broken_by_concurrency/comment_1_e043a71b60999cf97bd872d8b32fcac9._comment new file mode 100644 index 0000000000..592b8a45fa --- /dev/null +++ b/doc/bugs/tasty_test_limiting_broken_by_concurrency/comment_1_e043a71b60999cf97bd872d8b32fcac9._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="jkniiv" + avatar="http://cdn.libravatar.org/avatar/05fd8b33af7183342153e8013aa3713d" + subject="comment 1" + date="2022-05-24T02:46:17Z" + content=""" +Well done. Btw if somebody (like me) wonders why their tasty awk patterns '/like this/' don't work with `git-annex test -p` +in Windows Git Bash, one has to remember that Git Bash is based on Cygwin/Msys and there's a Unix -> Windows +path conversion at work. You can stop that conversion by prepending a space to the awk pattern ' /like this/' +or by setting the env var MSYS_NO_PATHCONV=1. So basically the above should be formulated as follows in this arguably hobbled environment: + +[[!format sh \"\"\" +$ MSYS_NO_PATHCONV=1 git-annex test -p '/concurrent get of dup key regression/ || /Init Tests/' +\"\"\"]] + +"""]]