Updates:
Cc: [email protected] [email protected] [email protected]
Labels: -mstone-3 Mstone-4
Comment #13 on issue 9177 by [email protected]: BMPImageDecoderTest.*Slow
too slow on valgrind and purify
http://code.google.com/p/chromium/issues/detail?id=9177
Moore's law will not help for milestone 3. :)
I'm inclined to mark this as fixed now that we're able to run some of the
decoder
tests. I don't know what value there is in keeping the bug open if we're
not going to
fix it.
Do we think we're losing coverage in the decoder code paths by not running
the slow
tests?
[I'm moving to mstone-4 so it doesn't block m3 and so we don't forget to
revisit this
before the next stable train.]
--
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
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
