Open GoogleCodeExporter opened 9 years ago
bisecting says that crrev.com/323900 is the culprit
Original comment by samu...@chromium.org
on 2 Jun 2015 at 11:45
Still not sure why the culprit CL caused this behavior, but it seems to be a
transient failure. Unfortunately, when ChromeDriver tries to check the frame id
and fails, it assumes that the frame is gone and switches to the top frame.
crrev.com/1150613004 adds a retry in the case where we get a
kNoSuchExecutionContext error from DevTools, which seems to be enough to work
around the problem.
Original comment by samu...@chromium.org
on 18 Jun 2015 at 7:36
Disabled the test in https://codereview.chromium.org/1231263002/
Original comment by gmanikp...@chromium.org
on 10 Jul 2015 at 11:41
Original issue reported on code.google.com by
samu...@chromium.org
on 2 Jun 2015 at 10:17