https://bugzilla.wikimedia.org/show_bug.cgi?id=46234
Ori Livneh <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Ori Livneh <[email protected]> --- Here's one run that seems bogus: https://wmf.ci.cloudbees.com/job/browsertests-windows-internet_explorer_9/267/testReport/(root)/Math/Display_simple_math/ Sauce job: https://saucelabs.com/jobs/302b2cf196374819b39470b2b3e55918# Raw selenium log: https://saucelabs.com/jobs/302b2cf196374819b39470b2b3e55918/selenium-server.log The failure is: org.openqa.selenium.NoSuchElementException: Unable to find element with id == wpTextbox1 (WARNING: The server did not provide any stacktrace information) ..but if you look at the video, #wpTextbox is clearly there. Interestingly, the first NoSuchElementException failure is thrown *before* another warning, "Invalid length: Content-Length=22200 written=8192". Although this warning is emitted for load.php (i.e., for one of the ResourceLoader requests and and not for the main request), it makes me suspect that Selenium is not waiting for DOMContentLoaded, and that there is consequently a race condition that causes the selector to fire some milliseconds before the element is present. If this is indeed the problem, it should be fixable by setting a wait timeout. See http://www.deanhume.com/Home/BlogPost/selenium-webdriver---wait-for-an-element-to-load/64 & http://docs.seleniumhq.org/docs/04_webdriver_advanced.jsp. -- You are receiving this mail because: You are on the CC list for the bug. You are watching all bug changes. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
