Comment #1 on issue 9519 by [email protected]: Make GTK+ failures
fatal in UI tests.
http://code.google.com/p/chromium/issues/detail?id=9519
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=12947
------------------------------------------------------------------------
r12947 | [email protected] | 2009-04-01 01:58:33 -0700 (Wed, 01 Apr
2009) | 9 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/chrome_dll_main.cc?r1=12947&r2=12946
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/chrome.gyp?r1=12947&r2=12946
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/ui/ui_tests.scons?r1=12947&r2=12946
Make Gtk/Gdk/GLib errors/warnings really fatal.
I had to disable RedirectTest because on Linux it triggered
Gdk assertion. It was a bug in our logging <-> glib logging
glue code that didn't make this test fail earlier.
http://crbug.com/9519
Review URL: http://codereview.chromium.org/56072
------------------------------------------------------------------------
--
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
-~----------~----~----~----~------~----~------~--~---
