Page MenuHomePhabricator

MobileFrontend editor and notifications sometimes take more than 5 seconds to load and cause browser tests to fail
Closed, DeclinedPublic

Description

https://integration.wikimedia.org/ci/job/mwext-mw-selenium/5201/console has been failing on the And the notifications overlay appears step intermittently.

This step seems to fail as it doesn't complete within the 5second default window. I expect the time to load the notifications overlay has regressed since now it depends on OOjs UI so must pull this library down when clicked (it didn't before).

  • We should update the test to increase the time out
  • We should explore ways of reducing the code size of Echo on mobile or finding sensible ways to increase what loads on page load.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Legoktm renamed this task from Notifications browser test has been flakey since porting to OOjs UI to MobileFrontend browser test has been flakey since porting notifications to OOjs UI.Mar 31 2016, 2:44 AM
Jdlrobson renamed this task from MobileFrontend browser test has been flakey since porting notifications to OOjs UI to Loading notifications speed regression due to porting notifications to OOjs UI.Apr 1 2016, 7:12 AM

This does not block using OOUI by default. I don't understand why this was linked to that task. Removing.

@Jdforrester-WMF is there a task tracking the size of OOjs UI? (I cant' find one)
This is the root cause and should block this task.

The regression in time from clicking notification icon to loading overlay was in the measure of seconds.

Jdlrobson renamed this task from Loading notifications speed regression due to porting notifications to OOjs UI to MobileFrontend editor and notifications sometimes take more than 5 seconds to load and cause browser tests to fail.Jul 4 2016, 6:33 PM
Jdlrobson added a project: Contributors-Team.

Reflecting reality.