From: Jim Meyering <meyering@redhat.com>
Date: Mon, 26 Mar 2012 11:52:58 +0000 (+0200)
Subject: tests: work around F17-valgrind sort-stale-thread-mem failure
X-Git-Tag: v8.16~1
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=cd65eb97987dc75cd3a7cf88a75544cf2854d870;p=platform%2Fupstream%2Fcoreutils.git

tests: work around F17-valgrind sort-stale-thread-mem failure

* tests/misc/sort-stale-thread-mem: Skip upon known failure.
---

diff --git a/tests/misc/sort-stale-thread-mem b/tests/misc/sort-stale-thread-mem
index 55fd139..78d1699 100755
--- a/tests/misc/sort-stale-thread-mem
+++ b/tests/misc/sort-stale-thread-mem
@@ -33,6 +33,13 @@ grep '^#define HAVE_PTHREAD_T 1' "$CONFIG_HEADER" > /dev/null ||
   seq -f %-98f 10000 | shuf > in ||
   framework_failure_
 
+# On Fedora-17-beta (valgrind-3.7.0-2.fc17.x86_64), this evokes two
+# "Conditional jump or move depends on uninitialised value(s)" errors,
+# each originating from _dl_start.
+# FIXME: change this to a framework_failure_ after release.
+valgrind --quiet --error-exitcode=3 sort --version > /dev/null ||
+  skip_ 'valgrind fails for trivial sort invocation'
+
 # With the bug, 'sort' would fail under valgrind about half the time,
 # on some circa-2010 multicore Linux platforms.  Run the test 100 times
 # so that the probability of missing the bug should be about 1 in