diff --git a/0001-tests-don-t-run-buf-oom-on-32-bit-systems.patch b/0001-tests-don-t-run-buf-oom-on-32-bit-systems.patch index 19335b9..d1240d9 100644 --- a/0001-tests-don-t-run-buf-oom-on-32-bit-systems.patch +++ b/0001-tests-don-t-run-buf-oom-on-32-bit-systems.patch @@ -1,4 +1,4 @@ -From 990e42d9c751d089cea161a25b7c2ade0a15d279 Mon Sep 17 00:00:00 2001 +From 415a8ae9c9b6ac18f0524b6af8e58408b426457d Mon Sep 17 00:00:00 2001 From: Edward Thomson Date: Thu, 13 Sep 2018 13:27:07 +0100 Subject: [PATCH] tests: don't run buf::oom on 32-bit systems @@ -6,14 +6,12 @@ Subject: [PATCH] tests: don't run buf::oom on 32-bit systems On a 32-bit Linux systems, the value large enough to make malloc guarantee a failure is also large enough that valgrind considers it "fishy". Skip this test on those systems entirely. - -(cherry picked from commit 415a8ae9c9b6ac18f0524b6af8e58408b426457d) --- tests/buf/oom.c | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/tests/buf/oom.c b/tests/buf/oom.c -index 16a03cc1a..86f5e7239 100644 +index 2741a8ddf2..ec3bad9979 100644 --- a/tests/buf/oom.c +++ b/tests/buf/oom.c @@ -11,12 +11,8 @@ @@ -59,6 +57,3 @@ index 16a03cc1a..86f5e7239 100644 } void test_buf_oom__grow_by(void) --- -2.19.1 -