mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-24 01:15:29 +02:00
Code Issues Wiki Activity

Bug 515307: Run test order of magnitude faster

Browse source 
The test was much too conservative on how long it waited for an event
to arrive. On my machine the time was 10 ms, so I set a baseline time
to wait of 100 ms allowing time for additional event to arrive.

Change-Id: Ic435d360e8781936682c19b838aeec13fa3d60bd
This commit is contained in:
Jonah Graham 2017-04-15 01:58:19 +01:00 • committed by Gerrit Code Review @ Eclipse.org
parent 501fa87934
commit 54f2d8770f
1 changed files with 7 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
dsf-gdb/org.eclipse.cdt.tests.dsf.gdb/src/org/eclipse/cdt/tests/dsf/gdb/tests/MIRegistersTest.java
View file

@ -442,8 +442,13 @@ public class MIRegistersTest extends BaseParametrizedTestCase {
new ServiceEventWaitor<IRegistersChangedDMEvent>(fSession, IRegistersChangedDMEvent.class);
writeRegister(registerDmc, regValue, formatId);
return eventWaitor.waitForEvents(TestsPlugin.massageTimeout(3000));
/*
* Wait long enough to find out if too few or too many events arrive. On
* my testing the expected events arrived within 10 ms, so this timeout
* allows 10x that amount of time for unexpected extra events to arrive.
*/
return eventWaitor.waitForEvents(TestsPlugin.massageTimeout(100));
}