From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Date: Sat, 9 Feb 2019 10:43:35 +0000 (+0100)
Subject: Fix gdb.multi/multi-arch-exec.exp blocking under high load/slow gdb
X-Git-Url: http://git.efficios.com/?a=commitdiff_plain;h=80047cfc27459d4d31fe275ddd02231d812ddb61;p=deliverable%2Fbinutils-gdb.git

Fix gdb.multi/multi-arch-exec.exp blocking under high load/slow gdb

When running multi-arch-exec.exp under valgrind, the test succeeds
when the machine is not loaded, but blocks when the machine is highly
loaded (e.g. when running the testsuite with valgrind with -j X
where X is one more than the nr of available cores).

The problem is that the hello program dies too early due to the alarm (30).

So, increase the alarm timer.
Note that this does not make the test take longer (it takes about
3.5 seconds on my system).  As I understand, the alarm is just there
to avoid hello staying there forever in case of another problem.

2019-03-28  Philippe Waroquiers  <philippe.waroquiers@skynet.be>

	* gdb.multi/hello.c (main): Increase alarm timer.
---

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 9f0065b016..4a4a87cf1c 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2019-03-28  Philippe Waroquiers  <philippe.waroquiers@skynet.be>
+
+	* gdb.multi/hello.c (main): Increase alarm timer.
+
 2019-03-28  Sandra Loosemore  <sandra@codesourcery.com>
 
 	* gdb.threads/watchpoint-fork.exp (test): Use large timeout
diff --git a/gdb/testsuite/gdb.multi/hello.c b/gdb/testsuite/gdb.multi/hello.c
index c079a18edd..b742a7345f 100644
--- a/gdb/testsuite/gdb.multi/hello.c
+++ b/gdb/testsuite/gdb.multi/hello.c
@@ -48,7 +48,7 @@ main()
 {
   int tmpx;
 
-  alarm (30);
+  alarm (240);
 
   bar();
   tmpx = hello(glob);