registration-attribute.https.html/registration-attribute.html are flaky due to the ordering between activate event and statechange event.
https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_tests&tests=registration-attribute
According to the failure log, sometimes statechange events are fired after the activate event. It's because of no guarantee of the order between ServiceWorkerMsg_ServiceWorkerStateChanged and ServiceWorkerEventDispatcher::DispatchActivateEvent. This could be problem even after mojoifying methods in SWProvider because there is no guarantee of the ordering between SWProvider and SWEventDispatcher. We have to consider the design of messaging.
Comment 1 by falken@chromium.org
, Aug 2 2017