Page MenuHomePhabricator

reasoning about javascript loading and test failures
Closed, DeclinedPublic

Description

abnormal load.php requests

this is essentially the same problem as shown with UploadWizard in https://bugzilla.wikimedia.org/show_bug.cgi?id=56483

When run in the Sauce Labs environment, tests for VisualEditor for Chrome display many many calls to ResourceLoader that are not shown in normal operation, nor in a browser test in a local environment.

At least some of these calls to load.php fail with javascript errors, thus causing VE to fail and the test to fail.

One recent example is shown at https://wmf.ci.cloudbees.com/job/VisualEditor-en.wikipedia.beta.wmflabs.org-linux-chrome/117/testReport/junit/(root)/VisualEditor%20Links/Enter_non_existing_link/

Here we see two distinct calls for the same code at ext.echo.alert, the second of which fails, see screen shot. In detail, the first call succeeds, the second fails:

[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.echo.alert%2Cbase%2Cdesktop%2Coverlay&skin=vector&version=20131021T193233Z&*

[200 OK] GET http://bits.beta.wmflabs.org/en.wikipedia.beta.wmflabs.org/load.php?debug=false&lang=en&modules=ext.echo.alert%2Cbase%2Cdesktop%2Coverlay&skin=vector&version=20131021T193233Z&*
Uncaught SyntaxError: Unexpected token ILLEGAL

Also in this particular run of the test find VE loading up code for ArticleFeedback and for Gadget code for DelAutoDropdown. VE loading gadget code in normal operation has been documented, see screen shot for invisible_iframe


Version: unspecified
Severity: normal
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=56483

Attached:

not_normal_RL_calls_error.png (621×718 px, 82 KB)

Details

Reference
bz56567

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:36 AM
bzimport set Reference to bz56567.

Created attachment 13691
gadget code in VE in normal operation

Attached:

invisible_iframe_contents.png (822×1 px, 172 KB)

Unless you can reproduce this outside of SauceLabs, I'm inclined to believe this is simply Chrome in SauceLabs being broken.