From 63a49d4df8a1f20be38e9bba907ecad24a34915e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 12 Dec 2016 13:31:58 -0400 Subject: [PATCH] comment --- ...omment_7_e31ee8f49bf5f73620209c524f1edb3d._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_7_e31ee8f49bf5f73620209c524f1edb3d._comment diff --git a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_7_e31ee8f49bf5f73620209c524f1edb3d._comment b/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_7_e31ee8f49bf5f73620209c524f1edb3d._comment new file mode 100644 index 0000000000..08e3364cac --- /dev/null +++ b/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_7_e31ee8f49bf5f73620209c524f1edb3d._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 7""" + date="2016-12-12T17:30:03Z" + content=""" +Can you please check if the current builds still have the "unable to +decommit memory" problem or not? + +(What it does after that error is probably nondeterministic, fixing that +error is the crucial thing.) +"""]]