kakoune/test/tools/git/blame-jump-message/script

while ! ui_out -until-grep draw_status | grep -v '\[fifo\]' >/dev/null;
do
    :
done
actual_draw_status=$(ui_out -until-grep draw_status)

expected_subject=$(cat <<'EOF'
2017-07-14 A U Thor "Don't break on single quotes or unbalanced {"
EOF
)
expected_subject_json=\"$(printf '%s' "$expected_subject" | sed 's/"/\\"/g')\"
expected_draw_status='{ "jsonrpc": "2.0", "method": "draw_status", "params": [[{ "face": { "fg": "black", "bg": "yellow", "underline": "default", "attributes": [] }, "contents": '"$expected_subject_json"' }], [{ "face": { "fg": "default", "bg": "default", "underline": "default", "attributes": [] }, "contents": "*git* 13:2 " }, { "face": { "fg": "black", "bg": "yellow", "underline": "default", "attributes": [] }, "contents": "[scratch]" }, { "face": { "fg": "default", "bg": "default", "underline": "default", "attributes": [] }, "contents": " " }, { "face": { "fg": "blue", "bg": "default", "underline": "default", "attributes": [] }, "contents": "1 sel" }, { "face": { "fg": "default", "bg": "default", "underline": "default", "attributes": [] }, "contents": " - client0@[kak-tests]" }], { "fg": "cyan", "bg": "default", "underline": "default", "attributes": [] }] }'

assert_eq "$actual_draw_status" "$expected_draw_status"
ui_out -ignore 2
Another try to fix blame-jump-message test flakyness 2024-02-18 09:00:33 +01:00			`while ! ui_out -until-grep draw_status \| grep -v '\[fifo\]' >/dev/null;`
Fix flaky blame-jump-message test This test fails occasionally[1] because the order of events and the number of events varies across runs. We should always call draw_status exactly 3 times: [git][fifo] [git] Commit subject etc. [git] Let's check it this way. This seems to work; this time I took the time to run it a couple hundred times and in Cirrus CI. [1] https://builds.sr.ht/~mawww/job/1151239 2024-02-18 01:16:53 +01:00			`do`
Another try to fix blame-jump-message test flakyness 2024-02-18 09:00:33 +01:00			`:`
Fix flaky blame-jump-message test This test fails occasionally[1] because the order of events and the number of events varies across runs. We should always call draw_status exactly 3 times: [git][fifo] [git] Commit subject etc. [git] Let's check it this way. This seems to work; this time I took the time to run it a couple hundred times and in Cirrus CI. [1] https://builds.sr.ht/~mawww/job/1151239 2024-02-18 01:16:53 +01:00			`done`
Another try to fix blame-jump-message test flakyness 2024-02-18 09:00:33 +01:00			`actual_draw_status=$(ui_out -until-grep draw_status)`
rc git.kak: fix blame-jump for commits with special characters Commit 53d9b9b67 (Escaping tweak in git.kak, 2024-02-06) broke blame-jump when the commit subject contains a single quote. (Also on unbalanced "{" which is a rare edge case but we already have it in our Git history.) git.kak assumes that filenames don't contain ' or unbalanced {, but we can't really make that assumption about people's names or commit subjects. Unfortunately the escaping here is very messy. We need to pass arbitrary text to callbacks; maybe we should have closures that can capture private temporary registers. 2024-02-12 23:48:29 +01:00
Fix flaky blame-jump-message test This test fails occasionally[1] because the order of events and the number of events varies across runs. We should always call draw_status exactly 3 times: [git][fifo] [git] Commit subject etc. [git] Let's check it this way. This seems to work; this time I took the time to run it a couple hundred times and in Cirrus CI. [1] https://builds.sr.ht/~mawww/job/1151239 2024-02-18 01:16:53 +01:00			`expected_subject=$(cat <<'EOF'`
rc git.kak: fix blame-jump for commits with special characters Commit 53d9b9b67 (Escaping tweak in git.kak, 2024-02-06) broke blame-jump when the commit subject contains a single quote. (Also on unbalanced "{" which is a rare edge case but we already have it in our Git history.) git.kak assumes that filenames don't contain ' or unbalanced {, but we can't really make that assumption about people's names or commit subjects. Unfortunately the escaping here is very messy. We need to pass arbitrary text to callbacks; maybe we should have closures that can capture private temporary registers. 2024-02-12 23:48:29 +01:00			`2017-07-14 A U Thor "Don't break on single quotes or unbalanced {"`
			`EOF`
			`)`
Fix flaky blame-jump-message test This test fails occasionally[1] because the order of events and the number of events varies across runs. We should always call draw_status exactly 3 times: [git][fifo] [git] Commit subject etc. [git] Let's check it this way. This seems to work; this time I took the time to run it a couple hundred times and in Cirrus CI. [1] https://builds.sr.ht/~mawww/job/1151239 2024-02-18 01:16:53 +01:00			`expected_subject_json=\"$(printf '%s' "$expected_subject" \| sed 's/"/\\"/g')\"`
			expected_draw_status='{ "jsonrpc": "2.0", "method": "draw_status", "params": [[{ "face": { "fg": "black", "bg": "yellow", "underline": "default", "attributes": [] }, "contents": '"$expected_subject_json"' }], [{ "face": { "fg": "default", "bg": "default", "underline": "default", "attributes": [] }, "contents": "git 13:2 " }, { "face": { "fg": "black", "bg": "yellow", "underline": "default", "attributes": [] }, "contents": "[scratch]" }, { "face": { "fg": "default", "bg": "default", "underline": "default", "attributes": [] }, "contents": " " }, { "face": { "fg": "blue", "bg": "default", "underline": "default", "attributes": [] }, "contents": "1 sel" }, { "face": { "fg": "default", "bg": "default", "underline": "default", "attributes": [] }, "contents": " - client0@[kak-tests]" }], { "fg": "cyan", "bg": "default", "underline": "default", "attributes": [] }] }'

			`assert_eq "$actual_draw_status" "$expected_draw_status"`
			`ui_out -ignore 2`