git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 1/1] t6300: fix match with insecure memory

From
Christian Hesse <list@eworm.de>
Date
Aug 21, 2023, 20:06 UTC
Message-ID
<20230821200645.36796-1-list@eworm.de>
From: Christian Hesse <mail@eworm.de>
Running the tests in a build environment makes gnupg print a warning:
gpg: Warning: using insecure memory!

This warning breaks the match, as `head` misses one line. Let's strip the line, make `head` return what is expected and fix the match.

Signed-off-by: Christian Hesse <mail@eworm.de>
---
 t/t6300-for-each-ref.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/t/t6300-for-each-ref.sh b/t/t6300-for-each-ref.sh
index 5b434ab451..488e358c8c 100755
--- a/t/t6300-for-each-ref.sh
+++ b/t/t6300-for-each-ref.sh
@@ -1764,7 +1764,7 @@ test_expect_success GPGSSH 'setup for signature atom using ssh' '
 
 test_expect_success GPG2 'bare signature atom' '
 	git verify-commit first-signed 2>out.raw &&
-	grep -Ev "checking the trustdb|PGP trust model" out.raw >out &&
+	grep -Ev "checking the trustdb|PGP trust model|using insecure memory" out.raw >out &&
 	head -3 out >expect &&
 	tail -1 out >>expect &&
 	echo  >>expect &&
-- 
2.41.0
Message 1 of 1 in “t6300: fix match with insecure memory”
  1. 1/1 t6300: fix match with insecure memoryChristian Hesse, Aug 21, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.