Community
Participate
Working Groups
3.2 M3 rcp.performance.EmptyWorkbenchPerfTest#testOpen() [close] This test finishes too fast and has been mostly failing for a 3.2 development
Paul, could you help out on this one?
These tests are running in less than 100ms. Shouldn't we write the test such that it executes for >100ms?
yes, although we need to take care that both the slow and fast machines run in a reasonable time.
This is still a problem in the performance test results for 3.2
*** This bug has been marked as a duplicate of bug 116284 ***