Comment #1 on issue 3789 by [EMAIL PROTECTED]: TimeTicks.TimerPerformance is flaky on a slow shared VM on a old P4 in debug http://code.google.com/p/chromium/issues/detail?id=3789
Basically this test is ensuring that we don't do anything which makes our timers be too slow. I've already downgraded the test severely to run on our test infrastructure - perhaps so much so that the test is useless. I see two options: 1) Consider this a real failure. Frankly, if it takes us 38ms just to get a time sample, our implementation of TimeTicks is hoarked, and the test is reporting a legitimate failure. 2) Turn off the assertion so that this test never reports a failure. This is a performance test, as it claims to be, but we could just allow arbitrary times. M-A: do you think we should just turn off the assertion? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to chromium-bugs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
