Fix build on ChromiumOS by ASSERTing TRUE in a UI test.

chrome/test/interactive_ui/keyboard_access_uitest.cc

Index: chrome/test/interactive_ui/keyboard_access_uitest.cc
diff --git a/chrome/test/interactive_ui/keyboard_access_uitest.cc b/chrome/test/interactive_ui/keyboard_access_uitest.cc
index f28575b06238f8166503efa9ac2f00f05d768eed..669b3bd394559b78a8c55da2d13927ed0b8ad230 100644
--- a/chrome/test/interactive_ui/keyboard_access_uitest.cc
+++ b/chrome/test/interactive_ui/keyboard_access_uitest.cc
@@ -112,7 +112,7 @@ TEST_F(KeyboardAccessTest, ReserveKeyboardAccelerators) {
       "</script></html>";
   scoped_refptr<BrowserProxy> browser(automation()->GetBrowserWindow(0));
   ASSERT_TRUE(browser);
-  browser->AppendTab(GURL("data:text/html," + kBadPage));
+  ASSERT_TRUE(browser->AppendTab(GURL("data:text/html," + kBadPage)));
   int tab_count = 0;
   ASSERT_TRUE(browser->GetTabCount(&tab_count));
   ASSERT_EQ(tab_count, 2);