it seems that BrowsingTestCase is quite problematic, after fixing this one, I'll re-factor the whole test case.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/5cd3126fe5f3a66e8e2fd0f134e3ec3caaab9f87

commit 5cd3126fe5f3a66e8e2fd0f134e3ec3caaab9f87
Author: liaoyuke <liaoyuke@chromium.org>
Date: Fri Apr 21 23:36:26 2017

Disable flaky testBrowsingPostToSamePage on devices.

testBrowsingPostToSamePage is flaky on devices. For example:

https://uberchromegw.corp.google.com/i/internal.bling.main/builders/
iphone10-device-x64/builds/4627

https://uberchromegw.corp.google.com/i/internal.bling.main/builders/
iphone10-device-x64/builds/4622

TBR=eugenebut@chromium.org

BUG=714303

Review-Url: https://codereview.chromium.org/2835563004
Cr-Commit-Position: refs/heads/master@{#466491}

[modify] https://crrev.com/5cd3126fe5f3a66e8e2fd0f134e3ec3caaab9f87/ios/chrome/browser/web/browsing_egtest.mm

Per last week's discussions, tests that are only disabled on devices should not be RBB, so removing the label.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/15e5376c4594bf810b8cbef076083c977aa98e43

commit 15e5376c4594bf810b8cbef076083c977aa98e43
Author: Yuke Liao <liaoyuke@chromium.org>
Date: Tue Jul 18 21:07:01 2017

Marking testPostFormToSamePage as flaky on device.

According to crbug.com/714303, testPostFormToSamePage was disabled on
devices due to flakiness, however, I couldn't repro locally as of
today, so I'm marking it as flaky on devices and see if it's still
reproducible on FYI bots.

Bug: 714303
Change-Id: I68bfc9d9771cbb00ac8161eb024cd8c52ee40244
Reviewed-on: https://chromium-review.googlesource.com/576290
Reviewed-by: Eugene But <eugenebut@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#487604}
[modify] https://crrev.com/15e5376c4594bf810b8cbef076083c977aa98e43/ios/chrome/browser/web/forms_egtest.mm

liaoyuke@, what is the status on this bug? Are you working on re-enabling it?

Yes, I will re-enable this test this week.

Is this test still flaky?