Closed Bug 1554311 Opened 5 years ago Closed 5 years ago

Start page timeout timer only after the test tab has actually been updated

Categories

(Testing :: Raptor, enhancement, P1)

Version 3
enhancement

Tracking

(firefox69 fixed)

RESOLVED FIXED
mozilla69
Tracking Status
firefox69 --- fixed

People

(Reporter: rwood, Assigned: rwood)

Details

Attachments

(1 file)

Currently the Raptor page timeout alarm/timer is set just before the test tab is updated with the test URL (ext.tabs.update call).

Instead, Raptor should await for the ext.tabs.update call itself to finish, and then at that time start the timeout timer. That way the elapsed time won't include the actual time for th eext.tabs.update call to finish; the timer will only measure the elapsed time it takes to actually get the performance measurements from the page content.

I am thinking that this may reduce Raptor intermittent page timeouts. Try this out and see how it effects timeouts etc.

Will capture the onerror (promise returned by ext.tabs.update) so if the tab update call itself fails then Raptor can force a timeout/end the test.

Note: Must check if this is compatible with Chromium.

Andrew, any thoughts about this potential patch? I'm thinking it may reduce some variability in the page timeout timer and ultimately reduce intermittent page timeouts (but not 100% sure; will do a bunch of try pushes to see if seems to have any effect).

Flags: needinfo?(acreskey)

Rob, I like this idea and I agree that it could make this step more deterministic.
Very curious as to how it behaves, but I think it's a better approach regardless.

Flags: needinfo?(acreskey)

Thanks Andrew! Unfortunately Chromium doesn't return a promise for chrome.tabs.update. However both Firefox and Chromium support a callback in the x.tabs.update call, so I'll try starting the page timeout timer only after that callback is invoked.

Pushed by rwood@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7cae42dee59f
Start page timeout timer only after the test tab has actually been updated r=acreskey
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: