From 296134f15d4f68aee5c12edc78a8df4c191ac354 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 18 May 2022 16:49:38 -0400 Subject: [PATCH] comment --- .../comment_2_dcc764525370338fbf9b6f2728e3e5ac._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/bugs/v8_conflict_resolution___40__adjusted_branch__41___teststuck/comment_2_dcc764525370338fbf9b6f2728e3e5ac._comment diff --git a/doc/bugs/v8_conflict_resolution___40__adjusted_branch__41___teststuck/comment_2_dcc764525370338fbf9b6f2728e3e5ac._comment b/doc/bugs/v8_conflict_resolution___40__adjusted_branch__41___teststuck/comment_2_dcc764525370338fbf9b6f2728e3e5ac._comment new file mode 100644 index 0000000000..aea3cf2772 --- /dev/null +++ b/doc/bugs/v8_conflict_resolution___40__adjusted_branch__41___teststuck/comment_2_dcc764525370338fbf9b6f2728e3e5ac._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2022-05-18T20:47:12Z" + content=""" +I've fixed that setEnv problem now, so the test suite is free of strange +segfault behavior, hopefully. And hopefully that will also avoid this bug +from happening more. +"""]]