From fa1ae3e862a6c2ee70948498c57234e95b3453c2 Mon Sep 17 00:00:00 2001 From: Kostya Kortchinsky Date: Wed, 27 Sep 2017 21:10:25 +0000 Subject: [PATCH] [scudo] Temporary disabling the valloc test on armhf Summary: Weird failure where `errno != ENOMEM` on valloc failure. The returned pointer is null since it passes the previous assert, so this shouldn't happen. http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-full/builds/10931 http://lab.llvm.org:8011/builders/clang-cmake-thumbv7-a15-full-sh/builds/2469 Disabling until we figure out what's going on. Reviewers: alekseyshl Reviewed By: alekseyshl Subscribers: aemerson, srhines, llvm-commits, kristof.beyls Differential Revision: https://reviews.llvm.org/D38324 llvm-svn: 314344 --- compiler-rt/test/scudo/valloc.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compiler-rt/test/scudo/valloc.cpp b/compiler-rt/test/scudo/valloc.cpp index 8764502..514a884 100644 --- a/compiler-rt/test/scudo/valloc.cpp +++ b/compiler-rt/test/scudo/valloc.cpp @@ -2,7 +2,7 @@ // RUN: %run %t valid 2>&1 // RUN: not %run %t invalid 2>&1 // RUN: %env_scudo_opts=allocator_may_return_null=1 %run %t invalid 2>&1 -// UNSUPPORTED: android +// UNSUPPORTED: android, armhf-linux // Tests that valloc and pvalloc work as intended. -- 2.7.4