Blame SOURCES/valgrind-3.9.0-gdbserver_tests-mcinvoke-ppc64.patch

2cd279
--- valgrind/gdbserver_tests/mcinvokeWS.vgtest	(revision 12990)
2cd279
+++ valgrind/gdbserver_tests/mcinvokeWS.vgtest	(working copy)
2cd279
@@ -4,7 +4,8 @@
2cd279
 args: 1 10000000 0 -S-S-S-S
2cd279
 vgopts: --tool=memcheck --vgdb=yes --vgdb-prefix=./vgdb-prefix-mcinvokeWS
2cd279
 stderr_filter: filter_make_empty
2cd279
-prereq: test -f vgdb.ptraceinvoker
2cd279
+# One some ppc64 installs this test just hangs
2cd279
+prereq: test -f vgdb.ptraceinvoker && ! `../tests/arch_test ppc64`
2cd279
 progB: invoker
2cd279
 argsB: 10 --vgdb-prefix=./vgdb-prefix-mcinvokeWS --wait=60 -c v.wait 0
2cd279
 # if the --wait is not enough, the test will fail or block
2cd279
Index: gdbserver_tests/mcinvokeRU.vgtest
2cd279
===================================================================
2cd279
--- valgrind/gdbserver_tests/mcinvokeRU.vgtest	(revision 12990)
2cd279
+++ valgrind/gdbserver_tests/mcinvokeRU.vgtest	(working copy)
2cd279
@@ -7,6 +7,8 @@
2cd279
 # as the Valgrind process is always busy, we do not need the vgdb.ptraceinvoker prereq.
2cd279
 # We even disable ptrace invoker to avoid spurious attach error message
2cd279
 # on kernels where ptrace is restricted.
2cd279
+# One some ppc64 installs this test just hangs
2cd279
+prereq: ! `../tests/arch_test ppc64`
2cd279
 progB: invoker
2cd279
 argsB: 10 --vgdb-prefix=./vgdb-prefix-mcinvokeRU --max-invoke-ms=0 --wait=60 -c v.wait 0
2cd279
 # if the --wait is not enough, the test will fail or block.