[Chromedriver] Re-enable ImplicitWaitTest.testShouldImplicitlyWaitForASingleElement on ChromePublic

[Chromedriver] Re-enable ImplicitWaitTest.testShouldImplicitlyWaitForASingleElement on ChromePublic

BUG=chromedriver:998
Committed: https://crrev.com/970ac6812ff04c3f44ae770b612b093b6feb5d80
Cr-Commit-Position: refs/heads/master@{#407234}

[gmanikpure, 2016-07-22 18:53:33]

gmanikpure@chromium.org changed reviewers:
+ samuong@chromium.org

[samuong, 2016-07-22 18:56:14]

lgtm

[gmanikpure, 2016-07-22 18:57:17]

The CQ bit was checked by gmanikpure@chromium.org

[commit-bot: I haz the power, 2016-07-22 18:57:51]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-22 19:49:12]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-22 19:51:05]

Description was changed from

==========
[Chromedriver] Re-enable
ImplicitWaitTest.testShouldImplicitlyWaitForASingleElement on ChromePublic

BUG=chromedriver:998
==========

to

==========
[Chromedriver] Re-enable
ImplicitWaitTest.testShouldImplicitlyWaitForASingleElement on ChromePublic

BUG=chromedriver:998

Committed: https://crrev.com/970ac6812ff04c3f44ae770b612b093b6feb5d80
Cr-Commit-Position: refs/heads/master@{#407234}
==========

[commit-bot: I haz the power, 2016-07-22 19:51:06]

Patchset 1 (id:??) landed as
https://crrev.com/970ac6812ff04c3f44ae770b612b093b6feb5d80
Cr-Commit-Position: refs/heads/master@{#407234}

[gmanikpure, 2016-07-25 15:57:32]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2176203002/ by gmanikpure@chromium.org.

The reason for reverting is: Test was re-enabled because the bots were running
against old chromedriver build having name "rNone" . But the test is still
failing on correct Head builds that confirms it's a real bug & hence needs to be
disabled again..