mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-30 20:35:38 +02:00
Code Issues Wiki Activity

Bug 518643: Increase wait for CDT to quit GDB

Browse source 
This is due to a new 500ms delay between inferior exiting and CDT
killing GDB.

Change-Id: I561f69e74caff3e82d89fd8cf2e4babe2c30392a
This commit is contained in:
Jonah Graham 2017-06-22 15:46:44 +01:00
parent 125220eb63
commit 8d26859710
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
dsf-gdb/org.eclipse.cdt.tests.dsf.gdb/src/org/eclipse/cdt/tests/dsf/gdb/tests/OperationsWhileTargetIsRunningTest.java
View file

@ -203,7 +203,8 @@ public class OperationsWhileTargetIsRunningTest extends BaseParametrizedTestCase
// The shutdown must happen quickly, which will confirm that it was
// our own terminate that did it. If it take longer, it indicates
// that the program terminated on its own, which is not what we want.
shutdownEventWaitor.waitForEvent(TestsPlugin.massageTimeout(500));
// See Bug 518643 for details as to length of this delay
shutdownEventWaitor.waitForEvent(TestsPlugin.massageTimeout(1000));
// Now make sure GDB is dead
Assert.assertTrue("GDB should have been terminated", !fControl.isActive());
@ -286,7 +287,8 @@ public class OperationsWhileTargetIsRunningTest extends BaseParametrizedTestCase
// The shutdown must happen quickly, which will confirm that it was
// our own terminate that did it. If it take longer, it indicates
// that the program terminated on its own, which is not what we want.
shutdownEventWaitor.waitForEvent(TestsPlugin.massageTimeout(500));
// See Bug 518643 for details as to length of this delay
shutdownEventWaitor.waitForEvent(TestsPlugin.massageTimeout(1000));
// Now make sure GDB is dead
Assert.assertTrue("GDB should have been terminated", !fControl.isActive());