Some of the flaky failures are caused by resource bundle issues. If you are
familiar with the build process, or the resource bundle, please take a look.
I'm pasting relevant parts of the logs:
C:\b\slave\chromium-dbg-builder\build\src\chrome\test\ui\ui_test.cc(227):
error: Value of: server_->WaitForInitialLoads()
Actual: false
Expected: true
C:\b\slave\chromium-dbg-builder\build\src\chrome\test\ui\ui_test.cc(161):
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:resource_bundle.cc(142)] Check failed: false.
C:\b\slave\chromium-dbg-builder\build\src\chrome\test\ui\ui_test.cc(175):
error: Value of: actual_crashes
Actual: 1
Expected: expected_crashes_
Which is: 0
Encountered an unexpected crash in the program during this test.
It seems to be hit in this code:
// We failed to retrieve the bitmap, show a debugging red square.
{
LOG(WARNING) << "Unable to load bitmap with id " << resource_id;
NOTREACHED(); // Want to assert in debug mode.
AutoLock lock_scope(lock_); // Guard empty_bitmap initialization.
static SkBitmap* empty_bitmap = NULL;
if (!empty_bitmap) {
// The placeholder bitmap is bright red so people notice the problem.
// This bitmap will be leaked, but this code should never be hit.
empty_bitmap = new SkBitmap();
empty_bitmap->setConfig(SkBitmap::kARGB_8888_Config, 32, 32);
empty_bitmap->allocPixels();
empty_bitmap->eraseARGB(255, 255, 0, 0);
}
return empty_bitmap;
}
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected]
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
