It would be great if the UI test framework printed out a stack trace when a [D]CHECK fails. -Darin
On Mon, Aug 17, 2009 at 9:35 AM, Paweł Hajdan Jr. <[email protected]>wrote: > I'm seeing a lot of these in the logs (most important message is bold): > > C:\b\slave\chromium-dbg-builder\build\src\chrome\browser\sessions\session_restore_uitest.cc(385): > error: Value of: last_tab->Reload() > Actual: false > Expected: true > C:\b\slave\chromium-dbg-builder\build\src\chrome\test\ui\ui_test.cc(485): > error: Value of: automation()->GetBrowserWindowCount(&window_count) > Actual: false > Expected: true > C:\b\slave\chromium-dbg-builder\build\src\chrome\test\ui\ui_test.cc(148): > error: Value of: assertions.size() > Actual: 1 > Expected: expected_errors_ > Which is: 0 > The following error(s) occurred in the application during this test: > *[FATAL:string_util.cc(515)] Check failed: IsStringASCII(utf16).* > C:\b\slave\chromium-dbg-builder\build\src\chrome\test\ui\ui_test.cc(162): > error: Value of: actual_crashes > Actual: 1 > Expected: expected_crashes_ > Which is: 0 > Encountered an unexpected crash in the program during this test. > > Do you know how this can happen? (intermittently!) Do you have some idea > how to debug it? > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
