SessionHistoryTest.FrameBackForward is probably no longer flaky.

chrome/browser/session_history_uitest.cc

Index: chrome/browser/session_history_uitest.cc
diff --git a/chrome/browser/session_history_uitest.cc b/chrome/browser/session_history_uitest.cc
index 5a597c474806ae6f2eb4f044398823dbc3807d20..7a6c0276588e0022862a8557ce0b2ace18769ff1 100644
--- a/chrome/browser/session_history_uitest.cc
+++ b/chrome/browser/session_history_uitest.cc
@@ -146,15 +146,8 @@ TEST_F(SessionHistoryTest, MAYBE_BasicBackForward) {
   EXPECT_EQ(L"bot3", GetTabTitle());
 }
 
-#if defined(OS_WIN) || defined(OS_MAC)
-// See http://crbug.com/61619
-#define MAYBE_FrameBackForward FLAKY_FrameBackForward
-#else
-#define MAYBE_FrameBackForward FrameBackForward
-#endif
-
 // Test that back/forward works when navigating in subframes.
-TEST_F(SessionHistoryTest, MAYBE_FrameBackForward) {
+TEST_F(SessionHistoryTest, FrameBackForward) {
   ASSERT_TRUE(test_server_.Start());
 
   // about:blank should be loaded first.