[Wikidata-bugs] [Maniphest] [Commented On] T90453: qunit test broken without explicitly setting $wgResourceLoaderMaxQueryLength

gerritbot added a comment. Change 200937 merged by jenkins-bot: Do not set $wgResourceLoaderMaxQueryLength for tests https://gerrit.wikimedia.org/r/200937 TASK DETAIL https://phabricator.wikimedia.org/T90453 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubs

[Wikidata-bugs] [Maniphest] [Commented On] T90453: qunit test broken without explicitly setting $wgResourceLoaderMaxQueryLength

gerritbot added a comment. Change 200937 had a related patch set uploaded (by JanZerebecki): Do not set $wgResourceLoaderMaxQueryLength for tests https://gerrit.wikimedia.org/r/200937 TASK DETAIL https://phabricator.wikimedia.org/T90453 REPLY HANDLER ACTIONS Reply to comment or attach file

[Wikidata-bugs] [Maniphest] [Commented On] T90453: qunit test broken without explicitly setting $wgResourceLoaderMaxQueryLength

gerritbot added a comment. Change 193130 merged by jenkins-bot: Change default of $wgResourceLoaderMaxQueryLength to 2000 https://gerrit.wikimedia.org/r/193130 TASK DETAIL https://phabricator.wikimedia.org/T90453 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !u

[Wikidata-bugs] [Maniphest] [Commented On] T90453: qunit test broken without explicitly setting $wgResourceLoaderMaxQueryLength

Tobi_WMDE_SW added a comment. For Wikidata this has been resolved so far by https://gerrit.wikimedia.org/r/196241. TASK DETAIL https://phabricator.wikimedia.org/T90453 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign . EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] [Commented On] T90453: qunit test broken without explicitly setting $wgResourceLoaderMaxQueryLength

adrianheine added a comment. In https://phabricator.wikimedia.org/T90453#1073327, @Krinkle wrote: > - The relevant software is incorrectly using the ResourceLoader module > system. (E.g. using it as a complete class registry.) This has all kinds of > scalability impacts and semantic "fragilenes

[Wikidata-bugs] [Maniphest] [Commented On] T90453: qunit test broken without explicitly setting $wgResourceLoaderMaxQueryLength

JanZerebecki added a comment. The test run without that setting failed even though it shows as green because --force was added as an argument to qunit. TASK DETAIL https://phabricator.wikimedia.org/T90453 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscri

[Wikidata-bugs] [Maniphest] [Commented On] T90453: qunit test broken without explicitly setting $wgResourceLoaderMaxQueryLength

Krinkle added a comment. This change (Ic416def846f361425c46f7b ) in general seems fine. However I'd like to see further evidence that the QUnit jenkins job is indeed failing because of this. And as a general practice it seems to me that requesting so

[Wikidata-bugs] [Maniphest] [Commented On] T90453: qunit test broken without explicitly setting $wgResourceLoaderMaxQueryLength

gerritbot added a subscriber: gerritbot. gerritbot added a comment. Change 193130 had a related patch set uploaded (by JanZerebecki): Change default of $wgResourceLoaderMaxQueryLength to 2000 https://gerrit.wikimedia.org/r/193130 TASK DETAIL https://phabricator.wikimedia.org/T90453 REPLY HAN